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 skills add attilaszasz/sdd-pilot --skill instructions-managementgit clone --depth 1 https://github.com/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/instructions-management)<a href="https://agentmods.dev/skills/attilaszasz/sdd-pilot/instructions-management"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/instructions-management/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/attilaszasz/sdd-pilot/instructions-management"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/instructions-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Prompt Injection · line 23 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 42 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00046 | $0.00901 |
| Opus 5 | $0.00023 | $0.00451 |
| Sonnet 5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
instructions-management 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 7d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions Management Guide
What are the Project Instructions?
project-instructions.md contains non-negotiable project principles gating all downstream decisions. Highest authority in the SDD process.
Template Structure (v2)
The current template (v2) has these mandatory sections:
## Core Principles— 3–7 numbered non-negotiable principles with MUST/SHOULD rules and rationale## Technology Stack— Language/Runtime, Frameworks, Storage, Infrastructure## Testing & Quality Policy— Coverage Target, Required QC Categories, Test Strategy, Linting/Formatting. QC extracts enforcement rules from keywords in this section.## Source Code Layout— Policy (ENFORCE_SRC_ROOT or PRESERVE_EXISTING_LAYOUT) and Convention## Development Workflow— Branching, Commit Convention, CI Requirements## Governance— Pre-filled defaults plus project-specific additions
Template version is tracked via <!-- template-version: 2 --> on the first line. Legacy templates (v1) lack structured sections and use [PRINCIPLE_N_NAME] placeholders.
Update Process
1. Load Current Project Instructions
- Read
project-instructions.md. - Identify all placeholder tokens:
[ALL_CAPS_IDENTIFIER]. - Adapt section count to user needs — fewer or more principles than template provides.
- Check template version:
<!-- template-version: 2 -->present → v2; missing → v1 (offer migration).
2. Collect Values for Placeholders
- Use values from user input (conversation).
- Infer from repo context (README, docs, prior versions) if not provided.
- Auto-detect from manifest files (package.json, Cargo.toml, etc.) for Technology Stack and Testing & Quality Policy sections.
LAST_AMENDED_DATE: today if changes made.- Version: see references/versioning-rules.md.
3. Draft Updated Content
- Replace every placeholder with concrete text.
- Preserve heading hierarchy and
<!-- template-version: 2 -->comment. - Principles: succinct name, non-negotiable rules, explicit rationale.
- Technology Stack: at minimum Language/Runtime must be populated.
- Testing & Quality Policy: use QC-recognised keywords so automated enforcement activates correctly. Keywords:
lint,static analysis,code quality,coverage,security,vulnerability,OWASP,WCAG,accessibility,benchmark,performance. - Governance: amendment procedure, versioning policy, compliance expectations.
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.
- 7d ago First seen · 80 lines · 46 tokens per session scan A 905ca4fea48a
instructions-management is a skill published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 901 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
spec-driven-task-implementer
Use this skill when an approved Spec-Driven change has reached Phase 4 and the user wants a task, phase, or full feature implemented from .specs/changes/ . It executes tasks in order, updates task status immediately, verifies each task before completion, and should not be used before implementation approval.
next
Phase 3 of the Tripod workflow, run repeatedly. Finds the first unchecked task in TASKS.md, implements it under the rules in CLAUDE.md, verifies its "Done when" condition, checks the box, and commits. Use when the user says "next task", "continue", "keep going", or invokes /tripod:next.
tasks
Phase 2 of the Tripod workflow. Reads SPEC.md and CLAUDE.md, then writes TASKS.md — an ordered list of small, scoped, verifiable tasks that implement the entire MVP. Use after the user has reviewed their spec, when they ask to "create tasks" or "break down the work", or when they invoke /tripod:tasks.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…