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 CassioRoos/godfly-skills --skill sentry-brief-v3git clone --depth 1 https://github.com/CassioRoos/godfly-skillsWrote 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/cassioroos/godfly-skills/sentry-brief-v3)<a href="https://agentmods.dev/skills/cassioroos/godfly-skills/sentry-brief-v3"><img src="https://agentmods.dev/badge/skills/cassioroos/godfly-skills/sentry-brief-v3/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/cassioroos/godfly-skills/sentry-brief-v3"><img src="https://agentmods.dev/badge/skills/cassioroos/godfly-skills/sentry-brief-v3.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.00057 | $0.00333 |
| Opus 5 | $0.00028 | $0.00167 |
| Sonnet 5 | $0.00011 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
sentry-brief 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 8d 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
Sentry Brief
An alert is data. A brief is a decision. Convert one into the other in under a screen.
Rules
- Blast radius before cause. Name who is currently harmed and how, before theorising about mechanism.
- Three discriminating checks. Every suspected cause ships with the check that would falsify it. A check that every hypothesis passes is not a check.
- Containment is separate from fix. State the action that stops harm now, even if it is ugly, and mark it as containment.
- Unknowns stay unknown. If the payload does not contain it, write "not in payload". Never infer a customer count, a region, or a dollar figure.
- One screen. If the brief does not fit on one screen it is not a brief.
Output
IMPACT -> who is harmed, right now, and how
SUSPECTS -> ranked causes, each with its discriminating check
CONTAIN -> the action that stops harm now
NEXT -> the single next diagnostic step and its owner
UNKNOWN -> what the payload does not tell us
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.
- 8d ago First seen · 38 lines · 57 tokens per session scan A 43fdb27ecc5b
sentry-brief is a skill published in the GitHub repository CassioRoos/godfly-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 333 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
code-remediate
Apply selected review fixes; bare PR targets use current online items, while PR +review adds the latest matching artifact.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
polish-code
Stage, format, lint, test, review, smoke test, and re-run itself until stable. Use when the user asks to "polish code", "refine code", "iterate on code quality", "review loop", "clean up, test, and review loop", or "run the polish loop".
simplify-code
Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes"…
java-code-review
Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a detailed review.md report with actionable comments and fixes.