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 magnus919/hermes-profiles --skill contribution-pipelinegit clone --depth 1 https://github.com/magnus919/hermes-profilesWrote 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/magnus919/hermes-profiles/contribution-pipeline)<a href="https://agentmods.dev/skills/magnus919/hermes-profiles/contribution-pipeline"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/contribution-pipeline/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/magnus919/hermes-profiles/contribution-pipeline"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/contribution-pipeline.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.00063 | $0.02587 |
| Opus 5 | $0.00032 | $0.01293 |
| Sonnet 5 | $0.00013 | $0.00517 |
| Haiku 4.5 | $0.00006 | $0.00259 |
Grade A, and why
contribution-pipeline 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 11d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribution Pipeline
Full lifecycle from assigned issue to merged PR. Five phases with concrete, falsifiable gates — no LLM-judged rubber stamps. Every phase produces an artifact that the next phase consumes. Every gate has a criterion that can fail.
This is a skill bundle. The orchestrator routes to sub-skills for specialized domains:
| Sub-Skill | Domain | When Loaded |
|---|---|---|
contribution-security |
Static analysis, secrets scanning, disclosure policies | P3.5 Security Gate |
contribution-test-quality |
Test design, change-detector prevention, scorecard | P2 Test Quality Gate |
contribution-documentation |
Code comments, commits, CHANGELOG, README, Mermaid | P2 Documentation + P4 PR Body |
contribution-clean-room |
Docker/VM verification, CI fingerprinting, environment classification | P3 Clean-Room Verification |
contribution-vault-integration |
Project fingerprint caching, knowledge graph persistence | P0 Caching + Cross-session |
Trigger Patterns
The skill accepts input through four patterns:
| Pattern | Input | Example |
|---|---|---|
| Issue-driven (primary) | Issue URL or owner/repo#number |
https://github.com/org/repo/issues/42 |
| Discovery-driven | Repo URL + issue description | "Found a bug in org/repo: X crashes when Y is null" |
| Kanban-driven | Kanban card with issue_url + repo metadata |
Card body parsed from structured fields |
| Cohort-driven | Multiple issue URLs sharing root cause | Consolidation detected → omnibus PR pattern |
Pre-flight checks before any phase begins:
- Issue exists and is open (not closed, not a discussion/RFC)
- No open PR already handles this issue
- No WIP PR in flight for this project (WIP limit: 1 per project, except <10-line fixes)
- Project's AI contribution policy allows agent-assisted contributions (check AGENTS.md, AI_POLICY.md)
- If this is a follow-up to an existing PR, verify that PR's merge status first. A PR with
state: MERGEDmeans branch fresh from main — do NOT push follow-up commits to a merged branch. A PR withstate: OPENmeans push to the same branch and update the PR body. Check viagh pr view <number> --json state,mergedAt.
What ships with it
6 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.
- 11d ago First seen · 153 lines · 63 tokens per session scan A 84461b23c35b
contribution-pipeline is a skill published in the GitHub repository magnus919/hermes-profiles (169 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 2,587 once invoked, about $0.0003 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
zero-script-qa
Zero Script QA — test without scripts using structured JSON logging and Docker monitoring. Triggers: zero-script-qa, log testing, docker logs, QA.
qa-phase
QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
regression-consistency-checker
Checks whether a new version of a repository preserves the behavior observed by tests on the old version. Use this skill when comparing two versions of code to detect regressions, verify refactoring safety, validate bug fixes don't break existing functionality, or ensure backward compatibility. Detects differences in…
merge-ready
Run all quality gates before merge — git hygiene, documentation completeness, code review, security audit, build, E2E, goal-backward verification, doc accuracy and UI/UX — then write the changelog entry.
verify-before-done
Proves work with tests, diffs, and logs before sign-off.