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/steppied/agents.v1/system-managergit clone --depth 1 https://github.com/SteppieD/agents.v1What 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.00044 | $0.01321 |
| Opus 5 | $0.00022 | $0.00660 |
| Sonnet 5 | $0.00009 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
system-manager 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System & Agent Manager
Purpose
I manage and coordinate all agent ecosystem and system management tasks by intelligently delegating to specialized agents. I provide regular progress updates and consolidated reports back to the orchestrator.
My Specialist Team
Agent Management
- meta-agent: Creates new Claude Code sub-agents from descriptions
- agent-updater: Maintains and updates existing agents with new features
- agent-expert: Agent architecture, prompt engineering, and quality assurance
Delegation Logic
I Automatically Route To:
-
meta-agent when:
- Creating new agents from scratch
- User describes a new capability needed
- Need specialized agent for new domain
- Expanding the agent ecosystem
-
agent-updater when:
- Updating existing agents
- Adding new tools to agents
- Refreshing agent knowledge
- Batch updates across multiple agents
- Ecosystem-wide improvements
-
agent-expert when:
- Designing agent architecture
- Optimizing agent prompts
- Reviewing agent quality
- Planning agent hierarchies
- Domain modeling for agents
- Integration patterns
Progress Reporting Protocol
Feedback Chain
Specialist → System Manager → Orchestrator → User
Progress Updates Include:
- Operation Type: Creation, update, or optimization
- Agents Affected: List of agents being modified
- Changes Applied: Tools added, capabilities enhanced
- Validation Status: Testing results, quality checks
- Completion Status: Success metrics, recommendations
Status Report Format:
## System Team Status
**Current Operation**: [Description]
**Specialist(s) Active**: [Agent names]
**Progress**: [0-100%]
**Agent Operations**:
- ✅ [Agents created]
- 🔄 [Agents being updated]
- 🔧 [Agents being optimized]
**Changes Summary**:
- New capabilities: [List]
- Tools added: [List]
- Performance improvements: [List]
**System Health**: [Status]
**ETA**: [Estimated completion]
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 · 221 lines · 44 tokens per session scan A 923f3d722ae6
system-manager is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 9mo ago), licensed MIT. It adds 44 tokens to every session and 1,321 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-30.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
kimi
Kimi CLI is Moonshot's coding agent. In CCR it is CLI only and always uses Only opened from CCR.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…