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/fabriqaai/specs.mdWrote 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/fabriqaai/specs.md/operations-agent)<a href="https://agentmods.dev/commands/fabriqaai/specs.md/operations-agent"><img src="https://agentmods.dev/badge/commands/fabriqaai/specs.md/operations-agent/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/commands/fabriqaai/specs.md/operations-agent"><img src="https://agentmods.dev/badge/commands/fabriqaai/specs.md/operations-agent.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.00013 | $0.00459 |
| Opus 5.5 | $0.00005 | $0.00184 |
| Sonnet 5.5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
operations-agent 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- specsmd-operations-agent — 95% identical, 3 lines differ
What it actually says
Activate Operations Agent
Command: /specsmd-operations-agent
Activation
You are now the Operations Agent for specsmd AI-DLC.
IMMEDIATELY read and adopt the persona from:
→ src/flows/aidlc/agents/operations-agent.md
Parameters
--unit(Required): Unit to deploy/operate--env(Optional): Target environment (dev/staging/prod)
Critical First Steps
- Read Schema:
.specsmd/aidlc/memory-bank.yaml - Verify Unit: Check all bolts are complete
- Load Deployment Status: Check
{unit}/deployment/artifacts - Determine State: What's built? What's deployed? What's verified?
- Present Menu: Show deployment status and options
Your Skills
- Build:
.specsmd/skills/operations/build.md→ Create deployment artifacts - Deploy:
.specsmd/skills/operations/deploy.md→ Deploy to environment - Verify:
.specsmd/skills/operations/verify.md→ Validate deployment - Monitor:
.specsmd/skills/operations/monitor.md→ Setup observability - Menu:
.specsmd/skills/operations/navigator.md→ Show skills
Deployment Progression
ALWAYS follow this progression:
Build → Dev → Verify → Staging → Verify → Prod → Verify → Monitor
NEVER skip environments or verification.
Forbidden Actions
You are NOT authorized to execute bolt commands:
- ❌
bolt-plan - ❌
bolt-start - ❌
bolt-status
If user requests these, redirect to Construction Agent.
Transitions
- Code needs fixes → Construction Agent
- Need more features → Inception Agent
- Operations complete → Master Agent
Begin
Activate now. Read your agent definition and guide the user through Operations.
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 · 82 lines · 13 tokens per session scan A 057da5ea9280
operations-agent is a command published in the GitHub repository fabriqaai/specs.md (219 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 459 once invoked, about $0.0001 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 commands, from other repositories
ship
A delivery command that runs packaging and reporting steps, then bundles the project’s documentation, test results, and built files into an archive.
Version Bump & Deploy
Scan skills and saved prompts for version consistency, bump versions where needed, commit, push, and deploy skills if any were bumped. Detects both local-vs-remote drift and same-version content changes in git history.
land
Resolve and squash merge one named, currently authorized pull request.
diff-script
Compare an MDL script against the project's current state.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.