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 skills add HoangNguyen0403/agent-skills-standard --skill monitor-respondgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/monitor-respond)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/monitor-respond"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/monitor-respond/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/skills/hoangnguyen0403/agent-skills-standard/monitor-respond"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/monitor-respond.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.00026 | $0.00953 |
| Opus 5.5 | $0.00010 | $0.00381 |
| Sonnet 5.5 | $0.00005 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
monitor-respond 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 28d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor Respond Skill
[!IMPORTANT] Turn a control-band breach or scheduled scan result into a tiered, evidence-backed response and a routed intake.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Monitor Respond Workflow
Goal: Convert a deterministic signal into the smallest sanctioned action and route the rest, instead of debugging or fixing on the strength of an alert.
Steps
- Load the signal:
- Read the control bands file (
docs/ops/bands.yaml; schema incommon-sdlc-metrics), the metric source, and the rolling baseline. - Confirm detection already ran deterministically; never classify a breach from narrative alone.
- Classify with the declared rules: 1 point beyond 3 sigma; 2 of 3 beyond 2 sigma same side; 4 of 5 beyond 1 sigma same side; 8 consecutive same side.
- Read the control bands file (
- Check for active harm first:
- Users affected now, or the band's
harm_checkmatches -> stop and route toincident-hotfix. - Otherwise continue at the tier the breach earned.
- Users affected now, or the band's
- Act at tier, never above it:
- 1 sigma: record the observation and stop.
- 2 sigma: diagnose read-only with the tier's declared tools; produce evidence, not a change.
- 3 sigma: propose a change as a pull request, or invoke a named pre-approved runbook from the band's routes.
- Missing tier definition, tools, or routes -> return BLOCKED rather than widening scope.
- Triage scheduled scan results:
security-testproduces the scan artifact; this workflow owns the baseline-versus-current diff.- For each new finding, either act or dismiss with a recorded reason; both outcomes tune the band.
- Carry unchanged findings forward without re-reporting them.
- Route the outcome:
- Diagnosis worth acting on ->
brainstorm-featurewithsource: control-band | security-scan, so it enters the normal requirement chain. - Shipped fix ->
retro-learnto add a permanent eval case for the class. - Repeated dismissals -> recalibrate the band before responding again.
- Diagnosis worth acting on ->
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.
- 28d ago Changed · +1 lines ea2f70d32add
- 1mo ago First seen · 92 lines · 26 tokens per session scan A ee9362d4354a
monitor-respond is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 953 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-09-25.
Other skills, from other repositories
intelligence-docs
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
react-idioms
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.
coordinate-pro
Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.
coordinate
Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.