aurora-agent: Skill for Claude Code

.agents/skills/classify-blueprint-modules/SKILL.md

classify-blueprint-modules is a skill for Claude Code, Codex from AURORA-NEURO/aurora-agent. It costs 72 tokens per session (2,723 once invoked), scanned A, original, Apache-2.0.

A guide for deciding whether sections of a software blueprint describe implementable code or only describe human activities. It defines five labels for classifying each section.

In plain words
What is it for?
Use it before opening a blueprint section, designing a crate, deciding what code can honestly cover, or reporting coverage figures.
Why use it?
It prevents teams from claiming code coverage for prose that software cannot actually implement and keeps coverage reports accurate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is AURORA-NEURO/aurora-agent's own configuration. It tells Claude Code and Codex how to work on aurora-agent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aurora-agent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AURORA-NEURO/aurora-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AURORA-NEURO/aurora-agent/main/.agents/skills/classify-blueprint-modules/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/AURORA-NEURO/aurora-agent

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 classify-blueprint-modules

README.md
[![agentmods](https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/classify-blueprint-modules.svg)](https://agentmods.dev/skills/aurora-neuro/aurora-agent/classify-blueprint-modules)
Your own site
<a href="https://agentmods.dev/skills/aurora-neuro/aurora-agent/classify-blueprint-modules"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/classify-blueprint-modules.svg" alt="Measured on agentmods" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,723 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.00072 $0.02723
Opus 5 $0.00036 $0.01362
Sonnet 5 $0.00014 $0.00545
Haiku 4.5 $0.00007 $0.00272

Measured 8d ago against content hash 76618a0737ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

classify-blueprint-modules 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 8d 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.

.agents/skills/classify-blueprint-modules/SKILL.md · 171 lines

How it starts

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

Classify blueprint modules

The blueprint ships 973 content modules. docs/COVERAGE.md excludes 214 of them as programme prose before counting anything, which leaves 759 code-bearing. That subtraction is not the end of the work — it is the beginning of it. The most valuable thing agents did in this workspace was keep going: reading a section's remaining modules and deciding, module by module, which of them a crate could honestly implement.

Do this before writing code, and report the classification as the headline. crates/stewardship opened §14 expecting eighteen modules of work and found six. That is a result, not a shortfall.

The test

One question, from crates/stewardship, reused by every crate since and quoted in crates/residue/src/verdict.rs:

Is the detailed design a set of predicates over an artifact, or a description of what people do?

A Council::vote() would assert only that a council met. Software cannot know that. A module whose strongest sentence is of that kind is not under-specified — it is not code.

The five verdicts

crates/residue/src/verdict.rs::Classification is the settled vocabulary. Reach for it rather than inventing a sixth name for the same distinction; two crates disagreeing about a module for reasons that are entirely about wording is a cost with no benefit.

Verdict What it means Where it was found
Process describes what people do crates/stewardship, 12 of §14's 18
ForeignArtifact code-bearing, precise, testable — and not Rust and not in this repository crates/devplat, 7 of 20 across §11 and §19
DischargedElsewhere implemented under a different section's id, by a crate that never names this one crates/worldfactory, §27
BlockLevelSplit the division runs inside the module, not between modules crates/bioevalx (§26/§07), crates/megafactory (§35)
GenuinelyUncovered nobody has read it, or it is real work not yet done the honest default

Read the full file on GitHub · 171 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. 8d ago First seen · 171 lines · 72 tokens per session scan A 76618a0737ff

Subscribe to this mod's changes

classify-blueprint-modules is a skill published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 2,723 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

halopsa

Every HaloPSA, HaloITSM and HaloCRM feature, plus a local SQLite store and cross-entity views the API can't return. Trigger phrases: triage my Halo queue, check SLA breaches in HaloPSA, who is overloaded in Halo, client card for Acme in Halo, Halo contract burn-down, what changed in Halo since this morning, find time…

Servosity/msp-skills · 104 tokens

veeam

Use when the user asks to check Veeam backup health across customers, find failing or stale backup jobs, surface workloads past their RPO, triage VSPC alarms, or report per-tenant license usage from a Veeam Service Provider Console. Syncs every tenant into a local SQLite mirror so it answers multi-tenant backup…

Servosity/msp-skills · 136 tokens

cipp

First single-binary CLI for CIPP - offline SQLite store, fleet posture analytics, and cross-tenant fan-out no other CIPP tool has. Trigger phrases: check MFA across all my tenants, find unused M365 licenses, offboard users from a CSV in CIPP, which tenants drifted off baseline, list CIPP tenants, use cipp, run…

Servosity/msp-skills · 89 tokens

immybot

Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions the web UI cannot. Trigger phrases: what failed in last night's maintenance window, which tenants are still on an old version of chrome, why didn't this computer get the deployment, what changed in the fleet since…

Servosity/msp-skills · 97 tokens

appdirect

Every documented AppDirect marketplace operation in one binary, plus offline sync and billing-reconciliation joins. Trigger phrases: reconcile appdirect billing, which appdirect payments failed this week, what changed in appdirect subscriptions, show my appdirect pipeline, appdirect company 360, use appdirect, run…

Servosity/msp-skills · 74 tokens

connectwise-manage

Every ConnectWise PSA workflow from the terminal - with a typed conditions query builder, offline SQLite sync, and cross-entity views (unbilled work, account 360, board triage) the PSA web UI can't give you. Trigger phrases: list connectwise tickets, triage the help desk board, find unbilled time in connectwise…

Servosity/msp-skills · 115 tokens