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 agentmods add skills/fusebase-dev/fusebase-flow/find-wasted-effortnpx skills add fusebase-dev/fusebase-flow --skill find-wasted-effortgit clone --depth 1 https://github.com/fusebase-dev/fusebase-flowWrote 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/fusebase-dev/fusebase-flow/find-wasted-effort)<a href="https://agentmods.dev/skills/fusebase-dev/fusebase-flow/find-wasted-effort"><img src="https://agentmods.dev/badge/skills/fusebase-dev/fusebase-flow/find-wasted-effort.svg" alt="Measured on agentmods" 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 | $0.00262 | $0.02710 |
| Opus 5 | $0.00131 | $0.01355 |
| Sonnet 5 | $0.00052 | $0.00542 |
| Haiku 4.5 | $0.00026 | $0.00271 |
Grade A, and why
find-wasted-effort 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 3d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Wasted Effort (A2 — process-per-outcome ceremony audit)
The process-per-outcome ceremony audit — the sibling of the tokens-per-rule /token-waste-audit (FR-26). Different axis, different inputs, shared discipline.
/find-wasted-effort (this) |
/token-waste-audit (FR-26) |
|
|---|---|---|
| Axis | process-per-outcome (ceremony) | tokens-per-rule (consumption) |
| Inputs | Flow artifacts ON DISK: gate/deploy reports, handoffs, approval artifacts, git log, round structure, prevents: annotations |
Claude Code transcripts (~/.claude/projects/.../*.jsonl) |
| Question | "Which ceremony step bought no safety outcome?" | "Which tokens bought no information?" |
| Shared | candidate/false-positive header · read-only-first posture · state/audit/<date>.md gitignored output |
(same) |
It is not standalone-with-no-sibling. It reuses the shipped substrate — see flow-skills/token-economy/SKILL.md and hooks/local/token-waste-audit.py for the FP-header text, the read-only posture, and the state/audit/ output convention. Do not reinvent or duplicate token-waste-audit's detection.
Guardrail first (same floor as FR-21 / FR-26)
Ceremony drops, safety never. This audit flags ceremony that is outcome-neutral in the observed window — that is a review candidate, not a remove instruction. A clean window is not proof a control is worthless: a gate stop can be low-frequency/high-severity (catastrophic-low-frequency, policies/ratchet-governance.yml). Every finding states the contrary evidence that would dismiss it; absence of contrary evidence in a short window is inconclusive, never confirmed.
Read-only-to-the-project is load-bearing (D4)
The analyzer writes only inside the gitignored state/audit/ directory — NO memory writes, NO overlay/spec/decisions/provider/policy edits, NO prune/remove application. This holds in Phase 1 (read-only) AND Phase 2A (proposal-output): Phase 2A enriches the output (a Proposed memory entries report section + an optional gitignored state/audit/ proposals JSON) but applies NOTHING. The audit describes candidates and proposes changes a human could apply; the PO owns subtraction (A3 prune protocol). The actual memory write-apply is Phase 2B (DEFERRED, consumer-repo prototype, AC2b). If asked to "just remove the dead gate" or "apply the proposal," refuse: "Per the A2 read-only-to-the-project posture (D4), I surface review candidates and propose patches; removal/apply is Phase 2B + the PO's call via the policies/ratchet-governance.yml prune protocol."
What ships with it
2 files 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.
- 3d ago First seen · 113 lines · 0 tokens per session scan A 0a88ec0440f4
find-wasted-effort is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 9d ago), licensed MIT. It adds 262 tokens to every session and 2,710 once invoked, about $0.0013 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
iblai-api-apply
Platform application gate — turn membership into an apply/review process. Applicant apply/renew/submit flows (drafts, file uploads, fees, withdrawal), reviewer pipeline (list, stats, detail, per-student decisions, notes, waivers, admin override submit, blocks), post-acceptance placement tests and course assignments…
iblai-api-crm
Manage an ibl.ai organization's CRM via the platform API — people, organizations, pipelines and stages, lead sources, deals (with stage-move/won/lost actions), activities, and tags. Org-wide sales/relationship management. Use for lead capture, pipelines, and deal flow.
iblai-api-agent-support
Manage an ibl.ai agent's human-support tickets via the platform API — list and filter the tickets users raised with an agent (by agent, requester, status, session), read a ticket's conversation thread, reply as the support team, change ticket status, and close or delete tickets. Use when triaging or responding to…
clickup-cli
ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user needs to interact with ClickUp — creating/editing tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Prefer this CLI over raw API calls.
iblai-api-invite
Manage ibl.ai organization user invitations via the platform API — list invites (accepted/pending) and send invites individually or in bulk (CSV rows), with optional group assignment. Use when inviting users into an organization.
bug
WHAT - Draft and review bugs using the Bug Template; classifies whether an issue should be escalated to incident based on production/user impact.