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 commands/ayoubben18/ab-method/analyze-projectgit 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.00000 | $0.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
analyze-project 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 2d 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.
What it actually says
Analyze Project
Description
Complete project structure analysis to understand architecture, patterns, and technical stack for effective AB Method task planning.
Usage
/analyze-project
Behavior
Loads and executes the analyze-project workflow from .ab-method/core/analyze-project.md
This workflow deploys 4 specialized subagents in parallel to produce:
UBIQUITOUS_LANGUAGE.md(root) — flat domain glossaryCONTEXT.md(root) — bounded-context overview (orCONTEXT-MAP.md+ per-context files for multi-context repos)docs/architecture/tech-stack.md— stack, entry points, external services, constraints, testing (merged)docs/architecture/frontend-patterns.md— components, state, routing, styling, API integrationdocs/architecture/backend-patterns.md— API, data, auth, services, background work
These are first drafts. To sharpen the domain language and capture decisions as ADRs, run /domain-model afterwards (interactive grilling session).
Workflow Details
- Domain Extraction - Inferred glossary + bounded-context skeleton from code
- Tech Stack Map - Single concise file covering stack, entry points, external services, constraints, testing
- Frontend Patterns - Client-side architecture
- Backend Patterns - Server-side architecture
Examples
/analyze-project
# Performs complete project analysis
# Creates comprehensive architecture documentation
# Documents tech stack, patterns, and constraints for future tasks
Alternative Usage
You can also use the traditional AB Method master controller:
/ab-master analyze-project
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.
- 2d ago First seen · 41 lines · 0 tokens per session scan A 4e5e86dc936a
analyze-project is a command published in the GitHub repository ayoubben18/ab-method (187 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.