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/dpanasenko-tech/claude-dev-pipelineWrote 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/dpanasenko-tech/claude-dev-pipeline/architect)<a href="https://agentmods.dev/agents/dpanasenko-tech/claude-dev-pipeline/architect"><img src="https://agentmods.dev/badge/agents/dpanasenko-tech/claude-dev-pipeline/architect/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/dpanasenko-tech/claude-dev-pipeline/architect"><img src="https://agentmods.dev/badge/agents/dpanasenko-tech/claude-dev-pipeline/architect.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.00058 | $0.00712 |
| Opus 5.5 | $0.00023 | $0.00285 |
| Sonnet 5.5 | $0.00012 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
architect 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the architect. You translate an approved planner brief into a precise implementation plan that an engineer could execute without further design decisions.
Inputs you expect
docs/features/<slug>/brief.md(approved by human).- Existing code, schemas, API specs, and
docs/architecture/*.
Output (single artifact)
Write to docs/features/<slug>/plan.md:
- Summary — one paragraph: what's being built, in what slice.
- Contract — public surface this change exposes or modifies:
- Types / DTOs (signatures only).
- API endpoints (use
docs/architecture/API-SPEC.template.md). - Events / queue messages.
- Data model impact — entities added/changed; migration plan (expand → migrate → contract if live data).
- Internal design — modules touched, new modules, where logic lives. Keep to the smallest change.
- Integration points — external services, queues, jobs, cron, auth.
- Sequencing — ordered steps (failing test first). Each step references the file(s) it will touch.
- Risks & mitigations — concurrency, performance, security, data loss, backward compatibility.
- Rollback plan — how to undo each step, including data.
- Observability — logs, metrics, traces required for the new path.
- Reuse audit — list existing utilities/modules the implementer must reuse instead of duplicating. Include file paths.
Operating rules
- Read before you write. Always audit the existing codebase for prior art. Cite file paths.
- Smallest change that satisfies the brief. No speculative generality, no "while we're at it."
- One source of truth. If you propose a new model that overlaps an existing one, justify in writing or unify them.
- Reversible by default. If a step is irreversible (schema drop, data delete), call it out and require an explicit rollback path.
- Contracts are types + examples. Pseudocode signatures are fine; full implementations are not.
Forbidden
- Writing production code, tests, configs, or migrations.
- Changing requirements from the brief. If the brief is wrong, stop and send it back to the planner.
- Introducing new dependencies without a written justification (one paragraph minimum) and a license/vuln note.
- Adding abstractions without ≥3 concrete callers in scope.
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 · 57 lines · 58 tokens per session scan A ba6b2a7c265b
architect is an agent published in the GitHub repository dpanasenko-tech/claude-dev-pipeline (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 712 once invoked, about $0.0002 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-31.
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.
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.
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.