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 stategit 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/state)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/state"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/state/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/state"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/state.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.00037 | $0.00465 |
| Opus 5.5 | $0.00015 | $0.00186 |
| Sonnet 5.5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
blueprint-repo-state 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
The repository, as it stands
The user cloned this repository and trusted the folder in Claude Code. Everything that follows commits, pushes and opens pull requests here, so it must start from exactly what GitHub has.
- Confirm the project folder is the repository root and
originis on GitHub.gh auth statusmust pass; if it does not, ask the user to rungh auth login(use the base pack'sguides/gh-login.md) and stop. - Add
.blueprint/as its own line to.git/info/exclude. That file is local to this clone and changes nothing in the repository; it keeps the build's notes from ever being committed. Never add it to.gitignore— that would be a change to their repository. - If the working tree has changes, ask what to do and stop. Never stash, reset, discard or commit someone else's changes.
- Check out the default branch (
sh <base pack>/checks/default-branch.shprints it) and bring it up to date withgit pull --ff-only. If that fails, ask.
Change nothing in the repository in this step — .git/info/exclude belongs to this clone, not to the
repository, and checking out or fast-forwarding the default branch changes nothing that is theirs.
Done when the check passes: the folder is the repository root, origin is on GitHub, gh is signed in,
.blueprint/ is excluded, the tree is clean, and the default branch matches origin.
Always
- Read
.blueprint/spec.mdif it exists. It is the agreed plan; do not widen it. - When you need a decision, ask it through the blueprint question tool and stop. Do not guess.
- Never force-push, rebase, or rewrite history. Never delete a branch you did not create.
- 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 · 33 lines · 37 tokens per session scan A e6f20fbca91a
blueprint-repo-state is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 465 once invoked, about $0.0001 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
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
review-pr
Perform a comprehensive code review of a pull request.