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 commands/systemowiec/ai-agents-workspace-starter/implementgit clone --depth 1 https://github.com/systemowiec/ai-agents-workspace-starterWrote 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/commands/systemowiec/ai-agents-workspace-starter/implement)<a href="https://agentmods.dev/commands/systemowiec/ai-agents-workspace-starter/implement"><img src="https://agentmods.dev/badge/commands/systemowiec/ai-agents-workspace-starter/implement.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.00006 | $0.00198 |
| Opus 5 | $0.00003 | $0.00099 |
| Sonnet 5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
implement 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 4d 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
Steps
- Read
.agents/roles/backend-engineer.md- Your role - Read
.agents/workflows/spec-development.md- MANDATORY flow - Read appropriate skills from
.agents/skills/ - Read
.agents/learnings/gotchas.md- known gotchas - Read
AGENTS.md- global rules
Workflow
- Analyze the task
- Propose a PLAN (files to change, modules, risks)
- Wait for plan approval
- Update documentation BEFORE code (Documentation First)
- Implement
- Run verification:
.agents/workflows/post-impl-verify.md - Run:
make lint && make test - Save report in
docs/specs/{layer}/{PREFIX}-NNN/impl-backend-engineer.md - Inform user: "Implementation complete. Report ready for review."
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.
- 4d ago First seen · 24 lines · 6 tokens per session scan A fa3a02aca3e6
implement is a command published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 198 once invoked, about $0.0000 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 commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.