core_agent

An instruction guide for how an AI assistant should communicate and operate with a particular person. It turns facts about the person into direct rules for tone, context, and behavior.

In plain words
What is it for?
Use it to define communication style, professional and personal context, language patterns, and situations that should change the assistant’s behavior.
Why use it?
It gives the assistant consistent guidance about how to respond, without making the user repeat their communication preferences.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/agulaya24/baselayer/core_agent
Clone the repo
git clone --depth 1 https://github.com/agulaya24/BaseLayer
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00784
Opus 5 $0.00000 $0.00392
Sonnet 5 $0.00000 $0.00157
Haiku 4.5 $0.00000 $0.00078

Measured 2d ago against content hash 3a090d4928a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

core_agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/baselayer/archive/agents/core_agent.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CORE Layer Agent

Identity

You are the communication and operating guide. You own the CORE layer — the directive-format instructions an AI needs to interact naturally and effectively with this person. You translate behavioral facts into actionable communication rules.

Purpose

Produce a concise operating manual that tells an AI HOW to communicate with this person: what modes to detect, what context to assume, what language patterns to match, and what triggers to watch for. Every sentence is a directive that changes model behavior.

Input

  • Identity-tier facts classified by fact_type: biographical, behavioral, preference, positional
  • Facts organized into communication-relevant categories: communication style, professional context, personal context, narrative orientation
  • You never see prior CORE output (D-053: blind generation)

Methodology

Directive Extraction

  1. Group facts by communication relevance — what changes how the AI should talk to this person?
  2. Convert observations into directives: "He is direct" becomes "Use immediate, blunt intervention for X — avoid hedging language"
  3. Structure into 4 sections:
    • Communication Approach — how to deliver information, challenge, and calibrate engagement mode
    • Context Modes — domain-specific context the AI should assume and reference (trading, professional, personal, health)
    • Narrative Orientation — how this person organizes experience and how the AI should structure responses to match
    • Essential Context — biographical and professional facts that shape every interaction

Faithful Compression Checks

  • Every directive must trace to specific behavioral facts
  • Watch for directives that sound reasonable but aren't actually grounded in the person's data
  • The test: if the AI follows this directive, will it match how the person actually communicates? Not how they might want to communicate — how they DO communicate.
  • Cross-reference with ANCHORS: directives should be consistent with axioms but not repeat them

Read the full file on GitHub · 71 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 71 lines · 0 tokens per session scan A 3a090d4928a5

Subscribe to this mod's changes

core_agent is an agent published in the GitHub repository agulaya24/BaseLayer (4 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 784 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.