Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jmylchreest/aidenpx agentmods add skills/jmylchreest/aide/implementWrote 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/jmylchreest/aide/implement)<a href="https://agentmods.dev/skills/jmylchreest/aide/implement"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/implement/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/jmylchreest/aide/implement"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.01902 |
| Opus 5.5 | $0.00004 | $0.00761 |
| Sonnet 5.5 | $0.00002 | $0.00380 |
| Haiku 4.5 | $0.00001 | $0.00190 |
Grade A, and why
implement 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 1mo 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Mode
Recommended model tier: smart (opus) - this skill requires complex reasoning
Focused TDD implementation: make failing tests pass with minimal code.
Purpose
This is the DEV stage of the SDLC pipeline. Tests already exist from the TEST stage. Your job is to write the minimal implementation that makes them pass.
Prerequisites
Before starting:
- Tests exist and are failing (from TEST stage)
- Design/spec is available (from DESIGN stage)
- You know which files to create/modify
Workflow
Step 1: Verify Tests Exist and Fail
# Run the tests - they MUST fail initially
npm test -- path/to/feature.test.ts
# or
go test ./pkg/feature/...
If tests pass: The work is already done. Mark complete and move on.
If tests don't exist: This is wrong - go back to TEST stage.
Step 2: Read the Tests
Understand what the tests expect:
- What functions/methods need to exist?
- What are the expected inputs and outputs?
- What edge cases are covered?
# If a large test file is unfamiliar, an outline can help locate relevant tests
mcp__plugin_aide_aide__code_outline file="path/to/feature.test.ts"
# Read relevant test sections directly when their ranges are known
Read path/to/feature.test.ts offset=<start> limit=<count>
# Read the full file when it is small or most tests are relevant
Read path/to/feature.test.ts
For related source, read known ranges or symbols directly. Use code_outline when unfamiliar
large-file structure would help select relevant code; read the full file when most contents are needed.
Batch known symbols with code_read_symbol (symbols, up to 10) when useful. Extra retrieval rounds
can outweigh smaller responses, so an outline is not a prerequisite to reading or editing.
Step 3: Check Design Decisions
Use mcp__plugin_aide_aide__decision_get with the feature topic to review decisions from DESIGN stage.
Use mcp__plugin_aide_aide__decision_list to see all project decisions.
Step 4: Implement Incrementally
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.
- 1mo ago Changed · +2 lines e7ffcd53e2c9
- 1mo ago First seen · 274 lines · 10 tokens per session scan A 64f33ee9214b
implement is a skill published in the GitHub repository jmylchreest/aide (19 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 1,902 once invoked, about $0.0000 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
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
implement
Use when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify. Enforces TDD: a failing test comes before the code that makes it pass, one task at a time, appended to a progress ledger that survives compaction. Delegates test tooling…
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
tdd
A test-driven development workflow based on repeating three stages: write a failing test, make it pass, then improve the code. The tests focus on what users can do through public interfaces rather than internal implementation details.
test-driven-development
Use when user explicitly requests test-driven development. Triggers: 'TDD', 'write tests first', 'red green refactor', 'test-first', 'start with the test'. Also invoked by develop and executing-plans for implementation tasks. NOT for: full feature work (use develop, which includes TDD internally).
writing-plans
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for…