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/maintainer-workspacegit clone --depth 1 https://github.com/event4u-app/agent-configWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/event4u-app/agent-config/maintainer-workspace)<a href="https://agentmods.dev/agents/event4u-app/agent-config/maintainer-workspace"><img src="https://agentmods.dev/badge/agents/event4u-app/agent-config/maintainer-workspace.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00454 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
.maintainer-workspace 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 5d 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.
What it actually says
agents/ — maintainer workspace AND dogfooded consumer convention
Explicit dual-role marker. Landed by
ADR-053; the boundary itself was established byADR-050.
This agents/ directory serves two roles at once, by design:
- The maintainer workspace for developing
@event4u/agent-config—roadmaps/,settings/,runtime/,decisions/,reports/,evidence/. - A compliant instance of the
agents/convention this package ships to consumer projects. The package dogfoods its own convention: maintaining it means living inside a compliant consumer-project structure.
Why the names overlap (this is not a bug)
The runtime settings loader (src/scripts/_lib/agent_settings.ts) anchors on a
directory literally named agents/ carrying convention markers (roadmaps/,
settings/.ai-council.yml, roadmaps-progress.md) and
reads .agent-settings.yml from agents/settings/. Those are convention
identifiers — the same strings a consumer project carries. Renaming this workspace would
either break the loader's convention coupling or force dual-path logic
("maintainer ⇒ X, consumer ⇒ agents/"), which is strictly worse than the
intentional overlap. See ADR-053 § Alternatives considered.
What this means for a reviewer
- A reference to
agents/…insrc/,docs/,templates/, or.agent-src/almost always describes the consumer convention, not this workspace. - This workspace's gitignored
.agent-settings.yml(underagents/settings/) is read at runtime; it must not move without the loader relocation-resilience guarantee proven intests/test_agent_settings_relocation_resilience.py. - The dual role is the forcing function that keeps the shipped convention usable.
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.
- 5d ago First seen · 36 lines · 0 tokens per session scan A a46e3f6a5bc8
.maintainer-workspace is an agent published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 454 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
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-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
meta-chrysalis
Orchestrate evolution writeback for MetaKim — aggregate signals, coordinate writeback through Warden's gate, and prevent recursive self-evolution.