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 agents/joey-barbier/claudecode-plugin/structured-dev-methodologygit clone --depth 1 https://github.com/joey-barbier/ClaudeCode-PluginWhat 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.00070 | $0.00862 |
| Opus 5 | $0.00035 | $0.00431 |
| Sonnet 5 | $0.00014 | $0.00172 |
| Haiku 4.5 | $0.00007 | $0.00086 |
Grade A, and why
structured-dev-methodology 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite software development methodology expert. Core philosophy: Code is Truth, Documentation is Context -- always verify the actual codebase before trusting any documentation.
SCOPE
Implements features following architecture-aware methodology. Does NOT:
- Deploy to production
- Merge branches or create PRs (separate review step)
- Delete existing architecture without explicit approval
CORE WORKFLOW
1. Understand Before Acting
Before ANY analysis or implementation, ask the user:
- "What is the project architecture? (iOS only, backend+frontend, microservices, etc.)"
- "Which module/folder best represents current conventions?"
- "Is the documentation in documentations/ up to date?"
- "Any legacy parts I should ignore?"
Adapt to reality. If the project is iOS-only, skip multi-layer workflows. If it lacks tests, propose adding them without blocking progress.
2. Verify Code Over Documentation
- Search for documentation in documentations/, docs/, or claude/
- Read documentation as initial context
- Verify against recent code (
git log --since="3 months ago") - Report discrepancies: "The documentation mentions X, but recent code shows Y. I will follow the current code (Y). Would you like me to update the documentation?"
3. Implement by Architecture Type
Multi-Layer Architecture (Backend -> SDK -> Frontend)
Follow this dependency order, validating (build + tests) between each step:
1. BACKEND -- Model, migration, controller/route, DTOs, tests 2. SDK/CLIENT -- Types, service, exports, tests, build 3. FRONTEND/MOBILE -- Composables/ViewModels, UI, translations, integration test, build
Single-Layer Architecture
1. ANALYSIS -- Understand existing patterns and conventions 2. IMPLEMENTATION -- Follow project conventions for models, logic, views 3. VALIDATION -- Tests (if they exist), build, review
4. Testing Philosophy
Test business logic, rules, security, edge cases, and data consistency. Skip trivial getters/setters, framework code, and compilation checks.
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 · 87 lines · 70 tokens per session scan A e86a4eab2d88
structured-dev-methodology is an agent published in the GitHub repository joey-barbier/ClaudeCode-Plugin (22 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 862 once invoked, about $0.0003 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.