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 ikenga-hq/ikenga-pkgs --skill ikenga-contributegit clone --depth 1 https://github.com/ikenga-hq/ikenga-pkgsWrote 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/ikenga-hq/ikenga-pkgs/ikenga-contribute)<a href="https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/ikenga-contribute"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/ikenga-contribute/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/ikenga-hq/ikenga-pkgs/ikenga-contribute"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/ikenga-contribute.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.00151 | $0.00869 |
| Opus 5 | $0.00076 | $0.00434 |
| Sonnet 5 | $0.00030 | $0.00174 |
| Haiku 4.5 | $0.00015 | $0.00087 |
Grade A, and why
ikenga-contribute 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 10d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ikenga-contribute
The contributor's copilot for Ikenga. Ikenga is a multi-repo,
Apache-2.0 project under github.com/ikenga-hq.
This skill lowers the friction of three things contributors do, and defers to the
project's own published conventions for everything (see lib/conventions.md).
This file is a router. Pick the action that matches the request, load that file
under actions/, and follow it.
Routing
| If the user wants to… | Load |
|---|---|
| Report a bug / request a feature / file any issue | actions/issue-draft.md |
| Open a pull request the right way (commits, changeset, tests, PR body) | actions/pr-workflow.md |
| Build + publish their first package | actions/pkg-onboard.md |
If the request spans two (e.g. "I fixed a bug, file the issue and open the PR"),
run issue-draft first, then pr-workflow, carrying the issue number forward.
Two rules that apply to every action
-
Consume conventions, never invent them. The repo→package-manager map, commit format, branch naming, which repos need a changeset, and the issue/PR template field-sets all live in the project, not in this skill.
lib/conventions.mdis a cached pointer; when in doubt, read the live source it names (ikenga-hq/.github/CONTRIBUTING.mdand the target repo's templates). Never tell a contributor a rule this skill made up. -
Confirm before anything outward-facing. This skill drafts; the human sends. Never run
gh issue create,gh pr create,git push, or any command that publishes — until you've shown the contributor the exact content and they've said go. Default to a dry-run preview.
A note on gh and issue templates
gh issue create --template <file> only pre-fills the template body as text —
it does not render GitHub's interactive issue forms (dropdowns/checkboxes). So
the correct path (used by issue-draft) is: read the target repo's template
field-set, collect answers via AskUserQuestion, assemble a filled Markdown
body, and pass it with gh issue create --body-file. Never rely on --web
alone (it abandons the contributor at a blank form) and never submit unconfirmed.
What ships with it
4 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.
- 10d ago First seen · 69 lines · 151 tokens per session scan A ebba476cf8dc
ikenga-contribute is a skill published in the GitHub repository ikenga-hq/ikenga-pkgs (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 151 tokens to every session and 869 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-31.
Other skills, from other repositories
ship
Use when ready to ship code to remote — handles direct push to main and PR-based feature branch flows. Do NOT use for partial workflows like just committing or just pushing.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.