agentmods.dev

operations-agent

A deployment-phase agent for AI-DLC, a development process that moves completed work through release environments. It builds release files, deploys them, checks the result, and sets up monitoring.

In plain words
What is it for?
Use it to build deployment artifacts, release a completed unit to an environment, verify the deployment, and configure monitoring.
Why use it?
It provides a fixed path from development to staging and production, with verification after each step to catch release problems early.

Command

203 8d ago A scan 13 tokens original MIT
View the source file fabriqaai/specs.md
Install

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.

agentmods
npx agentmods add commands/fabriqaai/specs.md/operations-agent
Clone the repo
git clone --depth 1 https://github.com/fabriqaai/specs.md
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 459 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00459
Opus 5 $0.00006 $0.00230
Sonnet 5 $0.00003 $0.00092
Haiku 4.5 $0.00001 $0.00046

Measured yesterday against content hash 057da5ea9280, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

src/flows/aidlc/commands/operations-agent.md · 82 lines

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

  1. Read Schema: .specsmd/aidlc/memory-bank.yaml
  2. Verify Unit: Check all bolts are complete
  3. Load Deployment Status: Check {unit}/deployment/ artifacts
  4. Determine State: What's built? What's deployed? What's verified?
  5. 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.

Changes

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.

  1. yesterday First seen · 82 lines · 13 tokens per session scan A 057da5ea9280

Subscribe to this mod's changes

operations-agent is a command published in the GitHub repository fabriqaai/specs.md (203 stars, last pushed 8d ago), licensed MIT. It adds 13 tokens to every session and 459 once invoked, about $0.0001 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.

Data and AIDevOps and cloudGit and workflowaiai-nativeai-native-engineeringdevelopmentdrivengenai
Related

Other commands, from other repositories

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

speckit.git.validate

Validate current branch follows feature branch naming conventions.

github/spec-kit · 8 tokens

speckit.assess.intake

Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.

github/spec-kit · 22 tokens

speckit.bug.assess

Assess a bug report (pasted text or URL) against the codebase and produce an assessment with possible remediation.

github/spec-kit · 22 tokens

proposal

Create a structured feature proposal in docs/11-proposals/.

mendixlabs/mxcli · 12 tokens

diff-script

Compare an MDL script against the project's current state.

mendixlabs/mxcli · 10 tokens