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/event4u-app/agent-config/commandgit 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.00047 | $0.00767 |
| Opus 5 | $0.00023 | $0.00383 |
| Sonnet 5 | $0.00009 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
agents 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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agents
Top-level orchestrator for the /agents family — the file-family
cluster: AGENTS.md, its multi-tool stubs (CLAUDE.md, GEMINI.md,
.github/copilot-instructions.md, .cursorrules), and the surrounding
agent infrastructure (rules, skills, pointers).
Looking for
agents/folder operations (scaffold, folder-audit, folder-cleanup)? Those live under/optimize agents-dir.
Sub-commands
| Sub-command | Routes to | Purpose |
|---|---|---|
/agents init |
commands/agents/init.md |
Bootstrap the agent layer — create AGENTS.md + tool stubs from the canonical template |
/agents optimize |
commands/agents/optimize.md |
Refactor AGENTS.md to the Thin-Root contract; propagate to multi-tool stubs |
/agents audit |
commands/agents/audit.md |
Read-only health check — token overhead, rule triggers, AGENTS.md health, stale references |
/agents user |
commands/agents/user.md |
User-persona file (.agent-user.md) — interview, render, maintenance |
Sub-command names match the locked contract in
docs/contracts/command-clusters.md.
Dispatch
-
Parse the user's argument:
/agents <sub-command> [args]. -
Look up the sub-command in the table above.
-
Load the body of the routed file and follow its
## Stepssection verbatim with the remaining args. -
If the sub-command is unknown or missing, print the table above and ask:
- init — bootstrap AGENTS.md + tool stubs
- optimize — refactor AGENTS.md to the Thin-Root contract
- audit — read-only health check on the agent layer
- user — manage
.agent-user.md(user-persona file)
Rules
- Do NOT commit, push, or open a PR unless the sub-command explicitly authorizes it.
- Do NOT chain sub-commands. One
/agents <sub>per turn. - If the user invokes
/agentswith no argument, show the menu — do not guess which sub-command they meant. - Edit
src/only.dist/agent-src/and.augment/regenerate from source.
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.
- yesterday First seen · 68 lines · 47 tokens per session scan A 2e2f93403d49
agents is an agent published in the GitHub repository event4u-app/agent-config (10 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 767 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 agents, from other repositories
meta-artisan
Match the right skills, tools, and capability packages for a MetaKim agent or workflow.
meta-scout
Discover external tools and skills to close MetaKim capability gaps.
meta-sentinel
Design security boundaries, hooks, permissions, and rollback rules for MetaKim agents.
meta-conductor
Design workflow orchestration, business-flow blueprints, stage sequencing, and rhythm control for MetaKim systems.
meta-chrysalis
Orchestrate evolution writeback for MetaKim — aggregate signals, coordinate writeback through Warden's gate, and prevent recursive self-evolution.
meta-prism
Review MetaKim outputs for quality drift, AI slop, and evolution signals.