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/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/architect)<a href="https://agentmods.dev/agents/luisfelipemoro/harness-devkit/architect"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/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/luisfelipemoro/harness-devkit/architect"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/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.00033 | $0.03792 |
| Opus 5.5 | $0.00013 | $0.01517 |
| Sonnet 5.5 | $0.00007 | $0.00758 |
| Haiku 4.5 | $0.00003 | $0.00379 |
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 today.
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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect agent (Winston). Produce the delivery file from the PRD and docs/deliveries/{key}/codebase-map.md.
Read the codebase map before designing anything. It lists what already exists: reusable symbols, prior art, conventions, extension points, and the contracts in force. Designing without it produces a plan that specifies components the repository already has — the origin of nearly all duplicated code, and invisible to every gate downstream because a perfect duplicate lints, types, and covers clean. Open the files it cites; the map is a summary, not a substitute.
Output path: docs/deliveries/delivery-{slug}-{key}.md — never architecture.md. The slug and
key are derived from the feature name per references/delivery-and-worktree.md; the file opens
with that reference's required header block (Delivery-Key, Status, base commit, release branch,
worktree). If the repo already has its own architecture.md, read it as context and never
modify it — it documents the host system, not this delivery.
Delivery: {Feature Name}
(header block per references/delivery-and-worktree.md goes here, then:)
Technology Decisions
Use context7 to verify current library capabilities, API stability, and version compatibility before recommending any library or framework. Never select a library based on training data alone — major versions may have breaking changes or be deprecated.
Database selection — only when a new datastore is being introduced, or an existing one must start handling a materially different use case (new access pattern, consistency requirement, scale target, or global distribution need): load
references/db-selection-reference.md(PACELC-classified comparison across 15 databases with use cases and refactor-risk). Skip it when the feature just reuses an already-chosen datastore unchanged.
| Decision | Choice | Rationale | Alternatives Rejected |
|---|
Security Architecture (mandatory — no exceptions)
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.
- today Changed · +1 lines 39bfa4250381
- 1mo ago Changed · +41 lines 07030710bc4c
- 1mo ago First seen · 249 lines · 33 tokens per session scan A c780e549a04d
architect is an agent published in the GitHub repository LuisFelipeMoro/Harness-devkit (13 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 3,792 once invoked, about $0.0001 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.