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/jmylchreest/aide/implementnpx skills add jmylchreest/aide --skill implementgit clone --depth 1 https://github.com/jmylchreest/aideWrote 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.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00010 | $0.01849 |
| Opus 5 | $0.00005 | $0.00924 |
| Sonnet 5 | $0.00002 | $0.00370 |
| Haiku 4.5 | $0.00001 | $0.00185 |
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 4d 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 — 274 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?
# For large test files, get the structure first
mcp__plugin_aide_aide__code_outline file="path/to/feature.test.ts"
# Then read specific test sections with offset/limit
Read path/to/feature.test.ts offset=<start> limit=<count>
# For small test files (<100 lines), reading the full file is fine
Read path/to/feature.test.ts
When implementing, use code_outline on adjacent/related source files to understand
their structure before reading them fully. This preserves context for the implementation work.
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
Write code to make tests pass one at a time:
- Pick the simplest failing test
- Write minimal code to pass it
- Run tests
- If passing, move to next test
- If failing, fix before proceeding
# Run specific test
npm test -- --grep "should create user"
# or
go test -run TestCreateUser ./pkg/...
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.
- 4d ago First seen · 274 lines · 10 tokens per session scan A 64f33ee9214b
implement is a skill published in the GitHub repository jmylchreest/aide (16 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 1,849 once invoked, about $0.0001 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-30.
Other skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用;包含 AI Coding 事件表语义,以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE,通常与 sls-dashboard-builder 一起使用。.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
alipay-webhooks
Receive and verify Alipay (Antom / Alipay+) webhook notifications. Use when setting up Alipay webhook handlers, debugging RSA256 Signature header verification, or handling payment events like notifyPayment, notifyCapture, notifyRefund, notifyAuthorization, and notifyDispute.
clio-webhooks
Receive and verify Clio (Clio Manage) webhooks. Use when setting up Clio webhook handlers, debugging X-Hook-Signature verification, completing the X-Hook-Secret handshake, or handling legal practice events like matter.created, contact.updated, activity.created, or bill events.