blueprint-repo-baseline

blueprint-repo-baseline is a skill for Claude Code, Codex from receptron/mulmoterminal. It costs 41 tokens per session (624 once invoked), scanned A, original, MIT.

A baseline check that finds the repository's own install, formatting, lint, type, build, and test commands and runs the applicable ones. It records the commands and proves the untouched code passes them.

In plain words
What is it for?
Use it at the start of a refactor or other code change to document and verify the project's checks.
Why use it?
Without a passing baseline, a later failure may already have existed and cannot be blamed on a change. This creates a known starting point before editing code.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it at the start of a refactor or other code change to document and verify the project's checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/receptron/mulmoterminal/baseline
Install

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.

Any agent
npx skills add receptron/mulmoterminal --skill baseline
Clone the repo
git clone --depth 1 https://github.com/receptron/mulmoterminal

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for blueprint-repo-baseline

README.md
[![agentmods](https://agentmods.dev/badge/skills/receptron/mulmoterminal/baseline/github.svg)](https://agentmods.dev/skills/receptron/mulmoterminal/baseline)
Your own site
<a href="https://agentmods.dev/skills/receptron/mulmoterminal/baseline"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/baseline/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.

agentmods 80×15 button for blueprint-repo-baseline

Your own site · 80×15
<a href="https://agentmods.dev/skills/receptron/mulmoterminal/baseline"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/baseline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 624 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00624
Opus 5.5 $0.00016 $0.00250
Sonnet 5.5 $0.00008 $0.00125
Haiku 4.5 $0.00004 $0.00062

Measured 19d ago against content hash 894960607f8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blueprint-repo-baseline 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 19d 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.

blueprints/repo/skills/baseline/SKILL.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Green before anything moves

Every later change claims "this behaves the same". That claim is measured against these gates, so they must be the repository's own, and they must be green on the untouched code. A gate that is already red cannot tell a regression from the state it was in.

  1. Package manager from the lockfile: yarn.lock → yarn, pnpm-lock.yaml → pnpm, package-lock.json → npm, bun.lockb/bun.lock → bun. The install command must not rewrite the lockfile: yarn install --frozen-lockfile, pnpm install --frozen-lockfile, npm ci, bun install --frozen-lockfile.
  2. Gates from package.json scripts, in this order when present: a format CHECK (format:check, never a script that rewrites files), lint, typecheck, build, test. Read what each script runs.
    • Leave out a script that needs a service, a browser download or network the machine may not have (test:e2e and the like), and write why in the record.
    • Read the CI workflows too: CI is the ground truth these approximate. A gate CI runs and package.json lacks is worth noting.
  3. Write .blueprint/gates.json:
    {
      "packageManager": "yarn",
      "install": "yarn install --frozen-lockfile",
      "gates": [{ "name": "lint", "command": "yarn lint" }, { "name": "test", "command": "yarn test" }],
      "skipped": [{ "name": "test:e2e", "why": "needs a browser download" }]
    }
    
    name is the script name exactly as package.json has it.
  4. Run the install, then every gate, and read each exit code — never the last line of output.
  5. If any gate is red on the untouched code, ask: it is the person's decision whether to fix it first (as its own change) or leave that gate out with a reason. Do not change the repository in this step.

Done when the check passes: every recorded gate exits 0 on the untouched default branch.

Always

  • Read .blueprint/spec.md if 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.
  • Change nothing in the repository in this step.
  • Say you are done by stopping; the executor runs the check. Do not claim success yourself.

Read the full file on GitHub · 43 lines

Changes

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.

  1. 19d ago First seen · 43 lines · 41 tokens per session scan A 894960607f8c

Subscribe to this mod's changes

blueprint-repo-baseline is a skill published in the GitHub repository receptron/mulmoterminal (239 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 624 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.

Related

Other skills, from other repositories

verify

Pre-commit verification entry point. Claude Code 2.1.286+ instructs the model to run a skill named verify right before committing (docs-only and tests-only commits exempt); this thin wrapper delegates that call to the MoAI quality gate instead of hand-rolling substitute checks.

modu-ai/moai-adk · 60 tokens

using-orc

If you were dispatched as a subagent to execute a specific task, skip this skill.

HigorAlves/orc · 31 tokens

clean-merge-lands-line-guard-on-a-value-neither-branch-predicted

Two branches each contain a guard, test or document that pins a line NUMBER in a third file, each side correctly re-aims that number for its own tree, and git merges both edits with NO conflict — leaving a merged tree whose real line can be neither number. Use when: (1) two parallel PRs both insert or delete lines in…

wan-huiyan/agent-traffic-control · 287 tokens

isolate-subagent-verification-from-live-worktree

A verification / gate-running subagent you dispatched into YOUR OWN worktree silently measures the branch PLUS your uncommitted edits, and reports the mixture as the branch's result. Nothing is clobbered and nothing errors — the suite really ran, the counts are real, they are just counts of a tree nobody will ever…

wan-huiyan/agent-traffic-control · 342 tokens

prove-test-failures-pre-existing-via-clean-worktree

After making a change you run the test suite and it shows failures — especially in files/areas your diff never touched, or a count that "feels unrelated." Before you either panic-debug them OR wave them off as "probably pre-existing," PROVE it: run the exact failing tests against a clean checkout of origin/main (a…

wan-huiyan/agent-traffic-control · 192 tokens

worktree-historical-test-replay-missing-dirs

Fix pytest exit 4 ("file or directory not found") when running a test command in a git worktree checked out at an OLD commit. Use when: (1) you're doing historical replay (incident replay, mutation testing, git bisect with tests) and the suite errors out in 1-2 seconds with no test execution, (2) the test command…

wan-huiyan/agent-traffic-control · 239 tokens