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/eduardohki/code-agent-plugins/shape-featuresnpx skills add eduardohki/code-agent-plugins --skill shape-featuresgit clone --depth 1 https://github.com/eduardohki/code-agent-pluginsWhat 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 | $0.00080 | $0.01819 |
| Opus 5 | $0.00040 | $0.00910 |
| Sonnet 5 | $0.00016 | $0.00364 |
| Haiku 4.5 | $0.00008 | $0.00182 |
Grade A, and why
shape-features 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 yesterday.
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.
Shape Features
Overview
Guided workflow for producing, auditing, or learning about software requirements. Routes to one of three sub-workflows based on the user's goal.
Quick Reference
| Goal | Workflow |
|---|---|
| Shape a new feature from any input | shape-new-feature-workflow.md |
| Audit or review existing requirements | review-existing-workflow.md |
| Learn what good requirements look like | learn-the-practice-workflow.md |
Each workflow opens with its own Required Reading section; the full reference list with loading guidance is in the Reference Index below.
Intake & Routing
Route directly when intent is clear from the user's message - do not present the menu first:
- User pastes requirements or a feature spec, or links to one → review-existing-workflow.md
- User describes a feature they want to build → shape-new-feature-workflow.md
- User asks "what makes good requirements" or similar → learn-the-practice-workflow.md
- User provides meeting notes or a product brief → shape-new-feature workflow (treat as input material)
- User has a feature in production and wants to refine the next iteration → review workflow (audit first, then re-plan)
The user may arrive with meeting notes, product briefs, external documentation, or a rough feature idea. All starting points are valid - the skill steers toward quality regardless of where the input came from.
Only when intent is genuinely ambiguous, present the menu and wait for a response before proceeding:
What would you like to do?
- Shape a new feature - collect and structure its requirements
- Review/audit existing requirements
- Learn what good requirements look like (and common pitfalls)
Not sure which applies? Starting fresh on a new feature → 1. Already have stories / a PRD / backlog items you want checked → 2. No specific feature yet, want to understand the practice first → 3.
What ships with it
15 files 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.
- assets/feature-requirements.md 6.0 KB
- README.md 12 KB
- references/adapting-to-your-context.md 11 KB
- references/bdd-and-acceptance-criteria.md 12 KB
- references/common-pitfalls.md 24 KB
- references/essential-principles.md 9.1 KB
- references/glossary.md 5.6 KB
- references/known-limitations.md 8.7 KB
- references/learn-the-practice-workflow.md 11 KB
- references/review-examples.md 21 KB
- references/review-existing-workflow.md 19 KB
- references/shape-new-feature-workflow.md 21 KB
- references/story-slicing-and-sizing.md 23 KB
- references/what-good-looks-like.md 8.4 KB
- references/worked-example.md 20 KB
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.
- yesterday First seen · 106 lines · 80 tokens per session scan A fbbc7cd95c9d
shape-features is a skill published in the GitHub repository eduardohki/code-agent-plugins (2 stars, last pushed 14d ago), licensed MIT. It adds 80 tokens to every session and 1,819 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.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.