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.
git clone --depth 1 https://github.com/joey-barbier/ClaudeCode-PluginWrote 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/agents/joey-barbier/claudecode-plugin/structured-dev-methodology)<a href="https://agentmods.dev/agents/joey-barbier/claudecode-plugin/structured-dev-methodology"><img src="https://agentmods.dev/badge/agents/joey-barbier/claudecode-plugin/structured-dev-methodology/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/joey-barbier/claudecode-plugin/structured-dev-methodology"><img src="https://agentmods.dev/badge/agents/joey-barbier/claudecode-plugin/structured-dev-methodology.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00070 | $0.00862 |
| Opus 5.5 | $0.00028 | $0.00345 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (21 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 862 once invoked, about $0.0003 per session on Opus 5.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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.