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 agentmods add skills/laurigates/claude-plugins/blueprint-autonomy-level3npx skills add laurigates/claude-plugins --skill blueprint-autonomy-level3git clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/blueprint-autonomy-level3)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-autonomy-level3"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-autonomy-level3.svg" alt="Measured on agentmods" 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.00045 | $0.02374 |
| Opus 5 | $0.00023 | $0.01187 |
| Sonnet 5 | $0.00009 | $0.00475 |
| Haiku 4.5 | $0.00005 | $0.00237 |
Grade A, and why
blueprint-autonomy-level3 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 2d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/blueprint:autonomy-level3
Scaffold the ADR-0020 autonomy level 3 pipeline — the highest rung of the blueprint automation model — into a consumer repo: two GitHub Actions workflows plus the deterministic scripts they call. Level 3 runs blueprint out of band (scheduled cron + a label-triggered executor), where levels 1–2 only run in-session. This repo (claude-plugins) dogfoods at level 1 and cannot exercise level 3 itself; a consumer repo opts in.
When to Use This Skill
| Use this skill when... | Use instead when... |
|---|---|
| A repo wants blueprint bookkeeping + work-order proposals to run on a schedule (no session open) | The in-session ambient pass is enough → /blueprint:autopilot (level 2) |
| A repo wants human-approved work orders executed into PRs automatically | You want to create/execute a work order by hand → /blueprint:work-order, /blueprint:prp-execute |
Auditing whether an already-scaffolded level-3 repo has drifted from the current templates (--check) |
Setting the autonomy level itself → edit docs/blueprint/manifest.json |
Context
- Automation config: !
bash ${CLAUDE_SKILL_DIR}/../../scripts/get-automation-config.sh - Blueprint present: !
find . -maxdepth 3 -path '*/docs/blueprint/manifest.json' - Autorun workflow already installed: !
find . -maxdepth 3 -path '*/.github/workflows/blueprint-autorun.yml' - WO-execute workflow already installed: !
find . -maxdepth 3 -path '*/.github/workflows/blueprint-wo-execute.yml'
Parameters
Parse $ARGUMENTS:
--check: audit-only. Diff the installed workflows/scripts against the plugin templates and reportPRESENT/DRIFT/ABSENTper file. Make no changes.- (no args): scaffold/install (idempotent — overwrites the managed files with the current template versions, re-syncing any drift).
Execution
Execute this level-3 scaffold.
Step 1: Verify preconditions
If the Context shows no docs/blueprint/manifest.json, stop with:
Blueprint not initialized — run /blueprint:init first. Nothing else.
What ships with it
1 file 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.
- 2d ago First seen · 162 lines · 45 tokens per session scan A 5d6cb7483d1a
blueprint-autonomy-level3 is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,374 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
code-review
CI code-review lane for a GitHub pull request. High-signal correctness and maintainability findings only, scoped out of security when a security lane exists. Use when: 'CI code review', 'claude-review lane', '/review:code-review', or a reusable workflow invokes the org code-review plugin command.
github-logs-analyze
Analyze GitHub Actions failure logs.
cicd
CI/CD pipeline patterns and deployment strategies for automated, reliable software delivery. Use when the user asks to design a build pipeline, choose a deployment model (blue-green, canary, rolling), configure environment promotion, manage build artifacts, implement zero-downtime deployments, set up quality gates, or…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…