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.
git clone --depth 1 https://github.com/SteppieD/agents.v1Wrote 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/steppied/agents.v1/system-manager)<a href="https://agentmods.dev/agents/steppied/agents.v1/system-manager"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/system-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/steppied/agents.v1/system-manager"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/system-manager.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.01321 |
| Opus 5.5 | $0.00018 | $0.00528 |
| Sonnet 5.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 1mo 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.
- 1mo 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 11mo ago), licensed MIT. It adds 44 tokens to every session and 1,321 once invoked, about $0.0002 per session on Opus 5.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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…