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.
npx agentmods add agents/agulaya24/baselayer/core_agentgit clone --depth 1 https://github.com/agulaya24/BaseLayerWhat 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.
| Model | Per session | Once 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 |
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.
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
- Group facts by communication relevance — what changes how the AI should talk to this person?
- Convert observations into directives: "He is direct" becomes "Use immediate, blunt intervention for X — avoid hedging language"
- 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
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.
- 2d ago First seen · 71 lines · 0 tokens per session scan A 3a090d4928a5
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.
Other agents, from other repositories
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
planner
Autonomous plan quality reviewer using Universal Planning Framework.
i18n
你是一个精通 Vue3 国际化架构的前端专家(专注于 Vue3 + TypeScript + Composition API)。同时,你也是一位专业的 UI/UX 翻译专家,擅长将中文界面语言翻译为地道、简洁的英文。.
chat-agent-spec
应实现于: /src/everlingo/agents/agent.py ,主要实现在 class MainAgent 。.
ko-translator
구조화된 영어 콘텐츠를 자연스러운 한국어로 번역. JSON 입력을 받아 번역된 JSON 출력. Medium 아티클 변환 파이프라인의 2단계.
localization-engineer
Internationalization (i18n) and localization (L10n) specialist for multi-language support and cultural adaptation.