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 wahidyankf/ose-public --skill producing-review-findingsgit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/producing-review-findings)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/producing-review-findings"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/producing-review-findings/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/wahidyankf/ose-public/producing-review-findings"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/producing-review-findings.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.00044 | $0.00978 |
| Opus 5.5 | $0.00018 | $0.00391 |
| Sonnet 5.5 | $0.00009 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
producing-review-findings 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Producing Review Findings
Finding Requirements owns what every finding carries. Discipline Roster owns each charter, and Cost and Noise Controls owns suppression. This skill covers the judgement a reviewer exercises before a finding leaves its hands.
Judge Against What the Change Set Out to Do
Read the linked plan or issue before the diff. A finding is worth raising only when it is both inside the change's declared scope and inside this discipline's charter.
A defect the change itself introduces is always in scope, however far it sits from the stated purpose. A remedy that is work the change never set out to do is an adjacent improvement: leave it for a follow-up. When the declared scope is missing, vague, or contradicted by the diff, that is itself a finding, raised against the description.
Outside the Charter, Note and Route
A real problem that another discipline owns is not raised here. Note it in the returned output for the coordinator, using the charter's routes-elsewhere column. Raising it anyway duplicates or contradicts the owning reviewer.
Raise Plainly or Not at All
A finding below the confidence floor is dropped, not softened into a remark. A finding above it is stated without hedging: shortening or sweetening a real defect to seem agreeable misleads the author as surely as a false finding does.
A Refutation Must Survive Its Own Fix
A refutation clause is only useful if it still tells right from wrong after the change is repaired. Test the defect, not something that happened to carry it:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 72 lines · 44 tokens per session scan A b2b39f866b8b
producing-review-findings is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 978 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
output-eval-error-analysis
Systematically review workflow traces to identify failure modes before building evaluators. Use when starting an eval project, after significant pipeline changes, or when production quality drops.
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
pr-conflict-refresh
Find every open PR that is CONFLICTING/DIRTY against current main after a merge wave, ping its assigned dev to merge main into their branch and push, and track the re-test status.
react-frontend
React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.
iterative-converging-audit
Run any "find all instances of X" sweep — a security audit, a safety audit, a code review, a research question, a compliance check — as an iterative loop that does NOT stop at one pass. Audit → fix → RE-audit → … until a clean pass returns zero NEW discoveries. Use whenever thoroughness matters and a single pass would…