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 JSONbored/awesome-claude --skill contributor-pipeline-gardeninggit clone --depth 1 https://github.com/JSONbored/awesome-claudeWrote 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/jsonbored/awesome-claude/contributor-pipeline-gardening)<a href="https://agentmods.dev/skills/jsonbored/awesome-claude/contributor-pipeline-gardening"><img src="https://agentmods.dev/badge/skills/jsonbored/awesome-claude/contributor-pipeline-gardening/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/jsonbored/awesome-claude/contributor-pipeline-gardening"><img src="https://agentmods.dev/badge/skills/jsonbored/awesome-claude/contributor-pipeline-gardening.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.00196 | $0.02395 |
| Opus 5.5 | $0.00078 | $0.00958 |
| Sonnet 5.5 | $0.00039 | $0.00479 |
| Haiku 4.5 | $0.00020 | $0.00239 |
Grade A, and why
contributor-pipeline-gardening 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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributor pipeline gardening — awesome-claude (HeyClaude)
HeyClaude is a curated registry/directory of Claude and AI-workflow assets, plus the website
(apps/web), registry/schema library (packages/registry), and MCP package (packages/mcp)
that serve it. This is a much smaller, quieter repo than loopover/metagraphed — as of
2026-07-17 it had zero open gittensor:*-labeled issues and a thin, fully-closed 2-milestone
history. This skill exists to build and then maintain a small, deliberately curated backlog —
15-25 contributor-available issues, not 50-100 — because padding a codebase this size to a
larger number would mean weak/duplicate issues, which is explicitly worse than a smaller real
backlog here.
The one thing this skill exists to prevent
Confirmed by the maintainer, 2026-07-17: contributors here have recently gravitated to
test(...): cover X PRs — real tests, but zero behavior change, added purely to nudge Codecov's
codecov/patch: 70% bar (a soft, easily-hit target — unlike loopover's 99% gate, 70% patch
coverage is trivially satisfied by testing already-written code). A second anti-pattern found
during this skill's initial research: issue #550 (a "growth sprint" umbrella with a long child
checklist) was being farmed almost entirely for its single easiest repeatable pattern — wiring
one more page into the existing intent-event/analytics-click convention, dozens of
near-identical PRs (#5205, #5202, #5201, ... #5168, all Made with Cursor), rather than any of
the umbrella's harder, more valuable child issues.
Never generate a standalone test(...): cover X issue. A regression test attached to a real
bug fix is fine and expected (see the template in reference.md); a test-only issue with no
behavior change is not. Never generate more instances of an already-being-farmed shallow
repeatable pattern (check open issues and recent merged-PR titles for a dense run of
near-identical titles before filing anything that looks like "wire pattern X into one more
file/page/route" — if 5+ near-identical PRs already exist for the same pattern, that vein is
farmed out, not a gardening opportunity). The whole point of this skill is issues that "drive
real value... website/content/features grow... fix bugs/issues in frontend/backend" (the
maintainer's own words) — not more of what a low-effort automated farmer already does better and
faster than a well-scoped issue ever could.
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.
- 1mo ago First seen · 140 lines · 196 tokens per session scan A 4694274abfa9
contributor-pipeline-gardening is a skill published in the GitHub repository JSONbored/awesome-claude (304 stars, last pushed 2mo ago), licensed MIT. It adds 196 tokens to every session and 2,395 once invoked, about $0.0008 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-08-30.
Other skills, from other repositories
request-progress
Group recent conversations into overall requests, review each one's progress from memory, link each to the owner goals it serves, and write the build story, so My Work shows progress meters, shipping velocity and learned working preferences. Use when asked to "group requests", "group by overall request", "review…
owner-goals
Map what the owner wants from the prompts they typed themselves (prompts an agent wrote are left out), then put their top priorities and open asks, each with dated quotes, in the Goals panel at the top of My Work. Use when asked for "owner goals", "my goals", "what do I want", "what am I asking for", "map my prompts"…
hivemind-goals
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/. Use whenever the user mentions a goal, objective, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item…
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.