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 rjmurillo/ai-agents --skill avoiding-manufactured-workgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/avoiding-manufactured-work)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/avoiding-manufactured-work"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/avoiding-manufactured-work/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/rjmurillo/ai-agents/avoiding-manufactured-work"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/avoiding-manufactured-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00088 | $0.00955 |
| Opus 5 | $0.00044 | $0.00477 |
| Sonnet 5 | $0.00018 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
avoiding-manufactured-work 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 4d 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.
Avoiding Manufactured Work
Detect follow-up work that exists because the agent wanted to keep helping, not because a real consumer asked for it.
Sibling skill
Pair this with the front-gate-before-pipeline pattern. Front-gate fires before work begins; this skill fires after work appears done. Same root cause (skipping self-evaluation under reward bias), opposite timing.
Triggers
is this work manufactured, does this follow-up have a consumer, classify this post-completion finding, should I file this follow-up
Process
- Name the concrete work product under review.
- Identify the consumer: user, issue, acceptance criterion, failing check, reviewer thread, or blocked downstream decision.
- If no consumer exists, stop. Do not create a task, issue, PR, memo, or research artifact.
- If a consumer exists, verify the proposed follow-up is the smallest action that unblocks that consumer.
- Report the disposition as one of: keep, shrink, defer, or delete.
Decision Rules
- Keep work that directly satisfies an acceptance criterion, fixes a failing required check, resolves a reviewer thread, or unblocks a named decision.
- Shrink work when the demand is real but the proposed scope exceeds what the consumer needs.
- Defer work when the demand is plausible but no current consumer is blocked.
- Delete work when it is speculative, reputational, performative, or created to make the agent appear thorough.
Output
Return:
Disposition: keep | shrink | defer | delete
Consumer: <named consumer or none>
Reason: <one sentence>
Next action: <smallest action, or none>
Disposition Procedure for Post-Completion Findings
The builder-ethos rule, section ## 4. Task Completion Contract, owns the completion contract (directory prefix omitted on purpose: this skill ships in the plugin mirrors, where a .claude/rules/ path dangles; look the rule up by name in whichever instruction tree you are reading, builder-ethos.md under .claude/rules/ or builder-ethos.instructions.md under the instructions trees): forming it, precedence, the terminal predicate, and reactivation. Read that section for any of those. Its ### Finding disposition subsection delegates exactly one step to this skill, verbatim:
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.
- 4d ago Changed · +31 lines · +20 tokens per session 452d28b5fc78
- 6d ago First seen · 41 lines · 68 tokens per session scan A dabcb96a0c4d
avoiding-manufactured-work is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 955 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-09-03.
Other skills, from other repositories
Deep Research Loop
Multi-step web research, compilation, and synthesis workflow. Scrapes multiple sources, cross-references claims, and produces a structured research brief.
lark-cli
Use when the user wants to operate Lark or Feishu via the local lark-cli (@larksuite/cli), including install, app credentials, OAuth, readiness checks, and safe read/write boundaries.
cron
Schedule reminders and recurring tasks.
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
notion
Use the Notion API to create, read, update Notion pages, data sources (databases), and blocks.
create-task
Create and verify recurring or one-shot reminders, scripts, agent jobs, reports, and interactive skill launches.