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 skills/event4u-app/agent-config/context-documentnpx skills add event4u-app/agent-config --skill context-documentgit clone --depth 1 https://github.com/event4u-app/agent-configWhat 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.00031 | $0.02206 |
| Opus 5 | $0.00015 | $0.01103 |
| Sonnet 5 | $0.00006 | $0.00441 |
| Haiku 4.5 | $0.00003 | $0.00221 |
Grade A, and why
context-document 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 3d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
context
When to use
Use this skill when:
- Documenting a module, service, or integration for future reference
- Exploring an unfamiliar area of the codebase
- Preparing for a feature that touches multiple areas
- Onboarding to a new part of the codebase
Do NOT use when:
- Writing code or features
- Creating roadmaps (use
roadmap-managementskill)
Procedure: Manage contexts
- Identify scope — Which area of the codebase needs a context document?
- Research — Use codebase-retrieval to understand the area (files, patterns, dependencies).
- Write or update — Create/update the context doc following the template below.
- Verify — Confirm all referenced files exist and descriptions match current code.
A context document is a structured snapshot of a codebase area:
- What it does, why it exists
- Key files, classes, and patterns
- Database tables and API endpoints
- Dependencies and known issues
Unlike feature plans (future-focused) or roadmaps (task-focused), contexts are present-focused — they describe the current state of the code.
File structure
.augment/contexts/ # Shared contexts (about the agent system itself)
├── augment-infrastructure.md
├── skills-and-commands.md
└── documentation-hierarchy.md
agents/settings/contexts/ # Project-wide contexts
├── {context-name}.md
{module_root}/{Module}/{agent_folder}/settings/contexts/ # Module-scoped contexts
├── {context-name}.md # Laravel: app/Modules/…
# Symfony: src/Bundle/…
# Monorepo: packages/…
.augment/templates/
└── contexts.md # Context template
Context types
| Type | Scope | Example |
|---|---|---|
| Module | Single module's structure and purpose | client-software.md |
| Domain | Business domain across modules | import-pipeline.md |
| Service | Complex service with its dependencies | customer-service.md |
| Integration | External API/system integration | probaus-api.md |
| Infrastructure | DevOps or infrastructure concern | queue-system.md |
| Knowledge card | Trust-tiered cache of expensive (remote) structural evidence — negative facts + pointers durable, positive structure a hypothesis | lodash.md, stripe-api.md |
| Standards card (Class A) | Coding standards derived from real tooling config — pointer + digest, trust: high (config-derived), auto-refreshed when the config changes; never a flattened claim |
coding-standards.md (points at ruff.toml, .editorconfig) |
| Lesson card (Class C) | A learned lesson — symptom (fact) split from hypothesis (decaying theory), trust: low, subject-not-person, anti-calcification decay; promoted only via the human gate (accumulation layer is eval-gated) |
agents/memory/curated/lessons/<slug>.md |
| Knowledge page (typed) | Team-shared, lifecycle-typed knowledge that grows while working a project — episodic sessions, semantic concepts, procedures on their way to a skill, small decisions | agents/knowledge/concepts/api-response-shape.md |
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.
- 3d ago First seen · 213 lines · 31 tokens per session scan A e142d245304e
context-document is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 2,206 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the eleven operating disciplines (prepaid billing, quote-before-spend, retryable…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…