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/ayoubben18/ab-method/sync-architecturenpx skills add ayoubben18/ab-method --skill sync-architecturegit clone --depth 1 https://github.com/ayoubben18/ab-methodWhat 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.00115 | $0.02221 |
| Opus 5 | $0.00057 | $0.01111 |
| Sonnet 5 | $0.00023 | $0.00444 |
| Haiku 4.5 | $0.00012 | $0.00222 |
Grade A, and why
sync-architecture 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 3d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Architecture (post-implementation)
Keep docs/architecture/* and the domain docs live by detecting, from a completed task's diff, what
the change introduced that the docs haven't caught up with — then proposing the exact doc deltas. It runs
in the same post-implementation phase as ../review-implementation/SKILL.md,
but asks a different question:
review-implementationasks "is this diff good code?" — this skill asks "does this diff introduce anything the docs don't yet know about?" The first is code debt; this is documentation drift.
It is the automated detection half of the manual /update-architecture workflow. Where
/update-architecture is a heavy, human-invoked pass (and also runs the improve-codebase-architecture
deepening loop), this skill is a lightweight detector that runs automatically after each task so the docs
stop silently drifting. It reuses /update-architecture's routing table — it does not invent its own.
Silence is the default output. A task that introduced nothing doc-worthy (a bug fix, styling, a trivial CRUD following existing patterns) produces no deltas — that is the normal case. A finding survives only if the docs are genuinely now wrong or incomplete. Never invent doc churn to look thorough.
ALWAYS check .ab-method/structure/index.yaml FIRST for where the architecture and domain docs live —
paths are user-configurable. Sweep only what this task changed — the cohesive diff across its missions
(git diff for the commit range) plus its progress-tracker.md mission summaries. This is not a
whole-repo doc audit.
Process
1. Gather diff + context
- The changed files and their
git difffor the task's commit range. - The task's
progress-tracker.mdMission Summaries — the per-mission Files / Built / Integrates with bullets already enumerate most of what's new. - The current architecture + domain docs, so the detector proposes only what's genuinely missing
(skip files that don't exist):
docs/architecture/tech-stack.md,frontend-patterns.md,backend-patterns.md,UBIQUITOUS_LANGUAGE.md,CONTEXT.md,docs/adr/.
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.
- 3d ago First seen · 131 lines · 115 tokens per session scan A cd0939feca19
sync-architecture is a skill published in the GitHub repository ayoubben18/ab-method (187 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 2,221 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…