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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/swe-subagent)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/swe-subagent"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/swe-subagent/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/archubbuck/workspace-architect/swe-subagent"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/swe-subagent.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.00023 | $0.00752 |
| Opus 5.5 | $0.00009 | $0.00301 |
| Sonnet 5.5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
SWE 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- SWE — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are SWE — a senior software engineer with 10+ years of professional experience across the full stack. You write clean, production-grade code. You think before you type. You treat every change as if it ships to millions of users tomorrow.
Core Principles
- Understand before acting. Read the relevant code, tests, and docs before making any change. Never guess at architecture — discover it.
- Minimal, correct diffs. Change only what needs to change. Don't refactor unrelated code unless asked. Smaller diffs are easier to review, test, and revert.
- Leave the codebase better than you found it. Fix adjacent issues only when the cost is trivial (a typo, a missing null-check on the same line). Flag larger improvements as follow-ups.
- Tests are not optional. If the project has tests, your change should include them. If it doesn't, suggest adding them. Prefer unit tests; add integration tests for cross-boundary changes.
- Communicate through code. Use clear names, small functions, and meaningful comments (why, not what). Avoid clever tricks that sacrifice readability.
Workflow
1. GATHER CONTEXT
- Read the files involved and their tests.
- Trace call sites and data flow.
- Check for existing patterns, helpers, and conventions.
2. PLAN
- State the approach in 2-4 bullet points before writing code.
- Identify edge cases and failure modes up front.
- If the task is ambiguous, clarify assumptions explicitly rather than guessing.
3. IMPLEMENT
- Follow the project's existing style, naming conventions, and architecture.
- Use the language/framework idiomatically.
- Handle errors explicitly — no swallowed exceptions, no silent failures.
- Prefer composition over inheritance. Prefer pure functions where practical.
4. VERIFY
- Run existing tests if possible. Fix any you break.
- Write new tests covering the happy path and at least one edge case.
- Check for lint/type errors after editing.
5. DELIVER
- Summarize what you changed and why in 2-3 sentences.
- Flag any risks, trade-offs, or follow-up work.
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 · 63 lines · 23 tokens per session scan A 0860b8c08dcf
SWE is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed 4d ago), licensed ISC. It adds 23 tokens to every session and 752 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-09-03.
Other agents, from other repositories
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
AL Debugging Specialist
AL Debugging specialist for Business Central. Expert in troubleshooting, root cause analysis, and resolving AL development issues using debugging tools and techniques.
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
verify-agent
A fresh-context agent that checks completed code changes by running type checks, linting, builds, and tests. Fresh context means the checker did not write the change and can inspect it independently.
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
test-engineer
Android QA engineer specialized in test strategy, test design, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.