Borrowing it
Nothing to install: this file belongs to dogganidhal/noddde. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dogganidhal/noddde/main/.claude/skills/spec-status/SKILL.mdgit clone --depth 1 https://github.com/dogganidhal/nodddeWrote 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/dogganidhal/noddde/spec-status)<a href="https://agentmods.dev/skills/dogganidhal/noddde/spec-status"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/spec-status/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/dogganidhal/noddde/spec-status"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/spec-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00053 | $0.01012 |
| Opus 5.5 | $0.00021 | $0.00405 |
| Sonnet 5.5 | $0.00011 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
spec-status 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 2mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Status Report
Scan all specs and report implementation status across the entire project, mapping each to its position in the 6-step pipeline.
Step 1: Gather Data
Find all spec files:
find specs/core specs/integration -name "*.spec.md" | sort
For each spec, extract:
titlefrom frontmatterstatusfrom frontmatter (draft|ready|implementing|implemented|superseded)source_filefrom frontmatterexportscountdepends_onlist
Step 2: Determine Pipeline Position
For each spec, check what artifacts exist:
| Has spec? | Has tests? | Has impl (no stubs)? | Tests pass? | Pipeline step |
|---|---|---|---|---|
| ✅ draft | — | — | — | Step 1 (needs review) |
| ✅ ready | ❌ | — | — | Between step 1-2 (needs /generate-tests) |
| ✅ ready | ✅ | ❌ stubs remain | 🔴 failing | Step 2 complete (RED tests, needs /implement-spec) |
| ✅ implementing | ✅ | 🔧 partial | 🔴 some fail | Step 3 in progress |
| ✅ implementing | ✅ | ✅ no stubs | ✅ passing | Step 4 complete (needs /validate-spec) |
| ✅ implemented | ✅ | ✅ no stubs | ✅ passing | Step 5 complete |
Check for:
- Test file existence at the expected path
- Stubs in source file:
grep "throw new Error" <source-file> - This is a lightweight check — don't actually run the full test suite
Step 3: Build Dependency Order
Using the depends_on graph, determine the recommended implementation order:
- Specs with no dependencies (leaves) should be implemented first
- Specs whose dependencies are all
implementedare ready to implement next - Specs with unimplemented dependencies are blocked
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.
- 2mo ago First seen · 106 lines · 53 tokens per session scan A af7cdc7fa0db
spec-status is a skill published in the GitHub repository dogganidhal/noddde (52 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,012 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-08-30.
Other skills, from other repositories
cratis-chronicle-client-typescript
Use when connecting a standalone Node.js process to Chronicle or diagnosing its decorators, discovery or client lifecycle. Not for React generated proxies or another language's client.
cratis-arc-command-typescript
Use when bootstrapping an Arc Node.js server or defining its TypeScript commands. Not for frontend proxy consumption, validation-only changes or server queries; use the corresponding Arc sibling.
cratis-arc-query-typescript
Use when declaring Arc Node.js read-model queries or observable endpoints. Not for React proxy consumption, server commands or Chronicle event materialization.
cratis-arc-validation-typescript
Use when adding rejection rules, state checks or validation assertions to an Arc Node.js server. Not for defining commands or queries, C# and JVM validators, or append-time uniqueness.
cratis-engineering-issue-hygiene
Use when claiming an issue, maintaining its status block or deciding an authorized closure or necessary follow-up. Not for delivery grouping, review rounds or CI operations.
cratis-screenplay-delivery-planning
Use when estimating an accepted Screenplay scope, ordering slice dependencies or dividing and tracking delivery across people or agents. Not for deciding model behavior, reviewing the model or rendering individual slices.