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/docsnpx skills add jmylchreest/aide --skill docsgit 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/docs)<a href="https://agentmods.dev/skills/jmylchreest/aide/docs"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/docs.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.00007 | $0.01290 |
| Opus 5 | $0.00003 | $0.00645 |
| Sonnet 5 | $0.00001 | $0.00258 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
docs 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 5d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Mode
Recommended model tier: balanced (sonnet) - this skill performs straightforward operations
Update documentation to accurately reflect the implemented code.
Purpose
This is the DOCS stage of the SDLC pipeline. Implementation is complete and verified. Your job is to ensure documentation matches reality.
What to Document
1. README Updates
If the feature affects how users interact with the project:
- Installation steps changed?
- New commands or options?
- New configuration?
- New dependencies?
2. API Documentation
If public APIs were added or changed:
- Function/method signatures
- Parameters and return types
- Usage examples
- Error conditions
3. Inline Documentation
If code needs explanation:
- Complex algorithms
- Non-obvious design decisions
- Integration points
- Edge cases
4. Architecture Docs
If structure changed:
- New components
- Changed data flow
- New dependencies between modules
Workflow
Step 1: Identify Changed Files
# See what was changed
git diff --name-only HEAD~5 # or appropriate range
# Find related docs
Glob for **/*.md
Glob for **/docs/**/*
Step 2: Check Existing Documentation
Read current docs that might be affected:
Read README.md
Read docs/api.md # if exists
Read CHANGELOG.md # if exists
Step 3: Read the Implementation
Understand what was built:
- Read the new code files
- Use
mcp__plugin_aide_aide__decision_getwith the feature topic to check design decisions - Use
mcp__plugin_aide_aide__decision_listto see all decisions
Step 4: Update Documentation
README.md Updates
Add/update sections as needed:
## New Feature
Description of what it does.
### Usage
\`\`\`bash
command --new-flag
\`\`\`
### Configuration
| Option | Type | Default | Description |
|--------|------|---------|-------------|
| newOption | string | "default" | What it does |
API Documentation
Document public interfaces:
### functionName(param1, param2)
Brief description.
**Parameters:**
- `param1` (string): What it is
- `param2` (number, optional): What it does. Default: 10
**Returns:** `Promise<Result>`
**Example:**
\`\`\`typescript
const result = await functionName("input", 20);
\`\`\`
**Throws:**
- `ValidationError`: When param1 is empty
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.
- 5d ago First seen · 270 lines · 7 tokens per session scan A 934428c977a4
docs is a skill published in the GitHub repository jmylchreest/aide (16 stars, last pushed 5d ago), licensed MIT. It adds 7 tokens to every session and 1,290 once invoked, about $0.0000 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.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
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.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…