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/dhar174/custom_github_copilot_agent_builder/specsmd-operations-agentgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote 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/dhar174/custom_github_copilot_agent_builder/specsmd-operations-agent)<a href="https://agentmods.dev/commands/dhar174/custom_github_copilot_agent_builder/specsmd-operations-agent"><img src="https://agentmods.dev/badge/commands/dhar174/custom_github_copilot_agent_builder/specsmd-operations-agent.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.00472 |
| Opus 5 | $0.00000 | $0.00236 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
specsmd-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 yesterday.
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.
This is a copy
95% identical to operations-agent — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description = "specsmd Operations Agent" prompt = """
description: Deployment phase agent - build, deploy, verify, and monitor releases
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.
- yesterday First seen · 85 lines · 0 tokens per session scan A 01caf1ae5ceb
specsmd-operations-agent is a command published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 472 tokens. A static security scan graded it A with 0 findings. It is 95% identical to operations-agent, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
account
This API allows you to manage your Scaleway Projects.
index
This documentation covers all available Dashmate CLI commands, their parameters, and behavior.
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.