Borrowing it
Nothing to install: this file belongs to JSONbored/loopover. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JSONbored/loopover/main/.claude/skills/contributor-pipeline-gardening/SKILL.mdgit clone --depth 1 https://github.com/JSONbored/loopoverWrote 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/loopover/contributor-pipeline-gardening)<a href="https://agentmods.dev/skills/jsonbored/loopover/contributor-pipeline-gardening"><img src="https://agentmods.dev/badge/skills/jsonbored/loopover/contributor-pipeline-gardening.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.1 | $0.00158 | $0.03616 |
| Opus 5 | $0.00079 | $0.01808 |
| Sonnet 5 | $0.00032 | $0.00723 |
| Haiku 4.5 | $0.00016 | $0.00362 |
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 8d 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
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 8d ago First seen · 121 lines · 158 tokens per session scan A 394be19fbbbb
contributor-pipeline-gardening is a skill published in the GitHub repository JSONbored/loopover (21 stars, last pushed today), licensed AGPL-3.0. It adds 158 tokens to every session and 3,616 once invoked, about $0.0008 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-30.
Other skills, from other repositories
hive.colony-progress-tracker
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a dbpath field.
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
Task Convention
Track multi-step work in useAgent's durable task manager, with .useagent/tasks.md as an explicit repo-local or offline fallback.
Group Collaboration
Best practices for inter-group communication, knowledge sharing, and collaborative workflows in four-tier architecture.
foundations-problem-solution-fit
Problem validation and solution design. Use when discovering customer problems, generating solution hypotheses, or defining MVP scope.