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 receptron/mulmoterminal --skill cigit clone --depth 1 https://github.com/receptron/mulmoterminalWrote 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/receptron/mulmoterminal/ci)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/ci"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/ci/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/receptron/mulmoterminal/ci"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/ci.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.00041 | $0.00383 |
| Opus 5.5 | $0.00016 | $0.00153 |
| Sonnet 5.5 | $0.00008 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
blueprint-repo-ci 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 27d 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.
What it actually says
Does CI run what we run?
Every later change is merged on the strength of CI, so CI has to run the gates recorded in
.blueprint/gates.json, on pull requests, from a clean install. This step only looks: anything it
finds missing becomes the first target of the plan, and is changed only after the person approves it.
- Read every workflow under
.github/workflows/. - For each recorded gate, find the workflow step that runs it on
pull_request. - Note every workflow without a top-level
permissions:block, and everyactions/checkoutwithoutpersist-credentials: false. - Look at CI on the default branch's current commit:
gh run list --commit $(git rev-parse HEAD). - Write
.blueprint/ci.json:
An empty{ "gaps": ["the typecheck gate is not run on pull requests", "ci.yml has no permissions: block"], "defaultBranchGreen": true }gapsmeans CI already covers everything.
Change nothing in the repository in this step. If the default branch is red in CI for a reason you cannot see locally, ask.
Done when the check passes: .blueprint/ci.json records the gaps (possibly none) and the state of CI on
the default branch.
Always
- When you need a decision, ask it through the blueprint question tool and stop. Do not guess.
- Say you are done by stopping; the executor runs the check. Do not claim success yourself.
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.
- 27d ago First seen · 36 lines · 41 tokens per session scan A ffef6069baf6
blueprint-repo-ci is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 383 once invoked, about $0.0002 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-09-28.
Other skills, from other repositories
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
pre-merge
The quality gate. Takes a feature branch from "eng says done" to "checked, fixed and ready for /merge". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → verdict. A…
project-release
Cut a release of this project (maven-decoder-mcp): draft notes, verify the gate, tag, push, watch CI, and confirm packages on PyPI, npm, Docker Hub, and GitHub. Use when the user says "release", "cut a release", "ship it", "tag a version", or asks about the release process, release notes, or publishing.