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 skills/stoa-platform/stoa/monitor-cdnpx skills add stoa-platform/stoa --skill monitor-cdgit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00027 | $0.00371 |
| Opus 5 | $0.00014 | $0.00186 |
| Sonnet 5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
monitor-cd 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 2d 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
Monitor CD — Continuous Deployment Verification
Run continuous CD verification after a merge to main.
Usage
/monitor-cd → runs /deploy-check every 5 minutes (default)
/monitor-cd 2m → runs every 2 minutes
Workflow
- Parse interval from
$ARGUMENTS(default:5m) - Use the
/loopcommand to schedule recurring/deploy-checkat the specified interval - Each iteration runs the full deploy-check:
- CI on main (latest workflow run)
- API health (api.gostoa.dev)
- Gateway health (mcp.gostoa.dev)
- Console + Portal (200 check)
- Pod status (kubectl)
- ArgoCD sync status
- Report results as a table after each check
- Stop automatically when all checks pass (verdict: Go)
Command
Run this:
/loop $ARGUMENTS /deploy-check
If $ARGUMENTS is empty, use 5m as default interval.
When to Use
- After merging a PR to main (especially code changes that trigger Docker build + ArgoCD sync)
- After a hotfix deployment
- When ArgoCD sync seems stuck
When NOT to Use
- For docs-only changes (no CD pipeline triggered)
- When you can verify manually with a single
/deploy-check
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.
- 2d ago First seen · 57 lines · 27 tokens per session scan A 9b475c4ddeb6
monitor-cd is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 371 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-31.
Other skills, from other repositories
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
csv-tools
Parse and analyze CSV data.