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/patternsnpx skills add jmylchreest/aide --skill patternsgit 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/patterns)<a href="https://agentmods.dev/skills/jmylchreest/aide/patterns"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/patterns.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.00017 | $0.01434 |
| Opus 5 | $0.00009 | $0.00717 |
| Sonnet 5 | $0.00003 | $0.00287 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
patterns 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern Analysis
Recommended model tier: balanced (sonnet) - this skill combines search with structured analysis
Analyze codebase patterns using static analysis findings. Surface complexity hotspots, code duplication, coupling issues, and potential secrets. Use this skill to understand code health and identify areas that need attention.
Prerequisites
Findings must be generated first by running analyzers via the CLI:
# Run all analyzers
./.aide/bin/aide findings run --path .
# Run specific analyzers
./.aide/bin/aide findings run --path . --analyzer complexity
./.aide/bin/aide findings run --path . --analyzer coupling
./.aide/bin/aide findings run --path . --analyzer secrets
./.aide/bin/aide findings run --path . --analyzer clones
Binary location: The aide binary is at .aide/bin/aide. If it's on your $PATH, you can use aide directly.
Available Tools
1. Search Findings (mcp__plugin_aide_aide__findings_search)
Full-text search across all findings. Supports Bleve query syntax for advanced searches.
Parameters:
query(required) — Search term or Bleve queryanalyzer(optional) — Filter to one analyzer:complexity,coupling,secrets,clonesseverity(optional) — Filter by severity:info,warning,criticalfile(optional) — Filter by file path substringlimit(optional) — Max results (default 20)
Example usage:
Search for: "high complexity"
-> findings_search query="complexity" severity="warning"
-> Returns: functions with high cyclomatic complexity, with file:line
2. List Findings (mcp__plugin_aide_aide__findings_list)
List findings with filters. Use when you want to browse rather than search.
Parameters:
analyzer(optional) — Filter to one analyzerseverity(optional) — Filter by severityfile(optional) — Filter by file path substringlimit(optional) — Max results (default 20)offset(optional) — Pagination offset
Example usage:
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 · 183 lines · 17 tokens per session scan A f90d184e940e
patterns is a skill published in the GitHub repository jmylchreest/aide (16 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 1,434 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.
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.