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 BingHanOfUESTC/open_agent_team --skill bug-risk-reviewgit clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_teamWrote 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/binghanofuestc/open_agent_team/bug-risk-review)<a href="https://agentmods.dev/skills/binghanofuestc/open_agent_team/bug-risk-review"><img src="https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/bug-risk-review/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/binghanofuestc/open_agent_team/bug-risk-review"><img src="https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/bug-risk-review.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.00000 | $0.00046 |
| Opus 5 | $0.00000 | $0.00023 |
| Sonnet 5 | $0.00000 | $0.00009 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
bug-risk-review 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 10d 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
Bug Risk Review
Look for:
incorrect conditions
missing error handling
state inconsistency
race conditions
backward compatibility breaks
data loss
edge cases
missing tests
Every finding needs evidence.
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.
- 10d ago First seen · 17 lines · 0 tokens per session scan A d0ffa511f911
bug-risk-review is a skill published in the GitHub repository BingHanOfUESTC/open_agent_team (109 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 46 tokens. 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.
Other skills, from other repositories
pr-check
PR review compliance: fetch review comments from an open PR, categorize as resolved/unresolved/dismissed, critically evaluate fixable items, implement approved fixes, and reply inline. Pass --unattended to halt on human-judgment items (emitted as Pending-Human) instead of prompting via AskUserQuestion.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting. Runs specialized review agents, scores findings, and submits a GitHub PR review via post-review.sh. Always executes post-review.sh to submit a review on every run (including zero-findings runs). Triggers…
council
Consult external AI council (Gemini 3.8 Flash, Codex, GLM-5.3, Kimi) for thorough reviews and consensus-driven decisions. Use ONLY when explicitly invoked with "/council" or when user says "consult the council", "invoke council", or "council review". Do NOT auto-trigger on generic phrases like "thorough review".
babysit
PR babysitter: monitors CI status, auto-rebases when behind, auto-fixes CI where possible, delegates review comment handling to dlc:pr-check, and re-requests review after fixes. Designed for /loop usage with Remote Control.
brainstorm
You MUST use this skill before /pm when work is ambiguous, scope is unclear, or multiple approaches exist. Explores problem space, proposes 2-3 approaches with trade-offs, and produces an approved spec document that feeds into both issue creation (/pm) and implementation planning (/cdt). Triggers: brainstorm, explore…
pr-validity
PR validity analysis: fetch PR diff, extract new code additions, search existing codebase for duplicate or overlapping implementations, classify changes, and create a structured GitHub issue.