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 rterakedis/leanwheel-skills --skill harvest-findingsgit clone --depth 1 https://github.com/rterakedis/leanwheel-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/rterakedis/leanwheel-skills/harvest-findings)<a href="https://agentmods.dev/skills/rterakedis/leanwheel-skills/harvest-findings"><img src="https://agentmods.dev/badge/skills/rterakedis/leanwheel-skills/harvest-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/rterakedis/leanwheel-skills/harvest-findings"><img src="https://agentmods.dev/badge/skills/rterakedis/leanwheel-skills/harvest-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.00071 | $0.03640 |
| Opus 5 | $0.00036 | $0.01820 |
| Sonnet 5 | $0.00014 | $0.00728 |
| Haiku 4.5 | $0.00007 | $0.00364 |
Grade A, and why
harvest-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 12d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 12d ago First seen · 169 lines · 71 tokens per session scan A c9932673eb70
harvest-findings is a skill published in the GitHub repository rterakedis/leanwheel-skills (2 stars, last pushed 8d ago), with no licence file. It adds 71 tokens to every session and 3,640 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
finding-reconciliation
Merge the independent A/B/C findings tables into one adjudicated ledger in 07-verification/documentation-verification-report.md — normalizing to the finding schema, deduplicating by location and claim, recording per-finding corroboration without downgrading single-pass findings, promoting cross-pass disagreement to…
scoring-and-release-gate
Score a documentation package against the ten-dimension weighted rubric in references/scorecard-rubric.md with a cited justification per dimension, then evaluate the nineteen conditions in references/release-gate-conditions.md and emit a binary release-ready, conditionally-ready, or not-ready verdict with…
contract-testing-flywheel
Generate a structured onboarding backlog — in Jira, GitHub Issues/Projects, Azure DevOps, or as a manual markdown export — that drives a development team from zero to publishing both consumer and provider contract tests. Use when the user invokes /contract-testing-flywheel or asks to "kick off contract testing for a…
engagement-scoping
Resolve the documentation engagement scope from the settings cascade — project identity, source roots, output root, delivery mode, action ceiling, confidentiality default, and the exact file set this run may touch — and freeze it to /00-control/.scope.json. Use when any /dossier: command starts, when the delivery mode…
project-modeling
Build one canonical project model — entities, boundaries, owners, lifecycle state, and end-to-end traces — and record its authoritative names in 00-control/terminology-and-ownership.md (TM-####), then project that single model into every audience view without ever forking it. Use when starting Phase 2, when the…
verification-protocol
Run one independent verification pass over a documentation package by attempting to falsify it — a coverage inventory rebuilt from the contracts rather than the index, a two-stratum claim sample, end-to-end traces executed against the sources, audience task simulation, and mechanics validation — emitting findings in…