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/rbah31/claude-code-workflow/monitoring-briefingnpx skills add rbah31/claude-code-workflow --skill monitoring-briefinggit clone --depth 1 https://github.com/rbah31/claude-code-workflowWrote 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/skills/rbah31/claude-code-workflow/monitoring-briefing)<a href="https://agentmods.dev/skills/rbah31/claude-code-workflow/monitoring-briefing"><img src="https://agentmods.dev/badge/skills/rbah31/claude-code-workflow/monitoring-briefing.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.00074 | $0.00410 |
| Opus 5 | $0.00037 | $0.00205 |
| Sonnet 5 | $0.00015 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
monitoring-briefing 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 5d 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
Monitoring Briefing
You are producing a quick monitoring status for the project owner, likely reading on a phone. Be concise.
Step 1 — Read reports
Read all files in monitoring/:
- monitoring/dependency-watch-latest.md
- monitoring/daily-brief-latest.md (if exists)
- monitoring/weekly-project-health-latest.md (if exists)
- monitoring/health-check-latest.md (if exists)
- monitoring/alerts/ (any files = active alerts)
Also read tasks/backlog.md header (P0/P1 items count).
Step 2 — Produce briefing
Format (strict — phone-readable):
🟢/🟡/🔴 PROJECT STATUS — [date]
Security: [clean / N vulnerabilities found]
Infra: [healthy / degraded / unknown if no report]
Docs: [in sync / N drift items]
Backlog: [N high, N medium, N low items]
Alerts: [none / list active alerts]
Action needed: [none / list actions]
Use 🟢 if everything clean, 🟡 if attention items exist, 🔴 if any CRITICAL alert or P0 backlog item.
Gotchas
- This is read on a phone. MAX 10 lines. No details unless asked.
- If a report file doesn't exist, say "no report yet" — don't error.
- If asked "more details on X", then expand that section only.
- Don't suggest fixes here. That's /remote-fix or /build territory.
STOP. Output the briefing and nothing else.
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.
- 5d ago First seen · 52 lines · 74 tokens per session scan A d209ba9d1edf
monitoring-briefing is a skill published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 410 once invoked, about $0.0004 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
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…