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/edit-spec/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/edit-spec)<a href="https://agentmods.dev/skills/dogganidhal/noddde/edit-spec"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/edit-spec/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/edit-spec"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/edit-spec.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 5 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.00039 | $0.00831 |
| Opus 5.5 | $0.00016 | $0.00332 |
| Sonnet 5.5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
edit-spec 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 1 (edit path): Edit an Existing Spec
Modify a behavioral specification while detecting breaking changes and managing downstream impact.
Pipeline step 1 of 6 (edit spec path). Called by the /spec orchestrator.
Step 1: Load Context
- Read the spec at the path provided (or find it: replace
packages/core/src/withspecs/core/and.tswith.spec.md) - Snapshot the current state before making changes — remember:
- Current
exportslist - Current type signatures in
## Type Contract - Current behavioral requirements (numbered list)
- Current handler signatures
- Current
depends_onlist
- Current
- Read the source file referenced in
source_fileto understand current implementation state - Read downstream specs — find all specs whose
depends_onincludes this module:grep -rl "<this-module-path>" specs/core/ specs/integration/
Step 2: Understand the Change
Classify the requested change:
| Change type | Examples | Risk level |
|---|---|---|
| Additive | New export, new behavioral requirement, new edge case, new test scenario | Safe |
| Clarification | Reword requirement, add detail to type contract, fix typo | Safe |
| Narrowing | Tighten a return type, add a required field, remove an optional behavior | ⚠️ Potentially breaking |
| Widening | Accept more input types, make a field optional, add a union variant | Usually safe |
| Removal | Remove an export, delete a behavioral requirement, drop a handler | 🔴 Breaking |
| Signature change | Different parameters, different return type, renamed type | 🔴 Breaking |
Step 3: Make the 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.
- 2mo ago First seen · 84 lines · 39 tokens per session scan A ce64671bbb68
edit-spec is a skill published in the GitHub repository dogganidhal/noddde (52 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 831 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.
cqrs-event-sourcing-architect
CQRS pattern, event stores, projections, eventual consistency. Activate on: CQRS, event sourcing, event store, read model, projection, aggregate, domain event, command handler. NOT for: message broker setup (use event-driven-architecture-expert), database optimization (use data-warehouse-optimizer).
enterprise-architecture-patterns
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability.