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/archubbuck/workspace-architect/software-engineer-agent-v1git 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/software-engineer-agent-v1)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/software-engineer-agent-v1"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/software-engineer-agent-v1.svg" alt="Measured on agentmods" 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.00036 | $0.02082 |
| Opus 5 | $0.00018 | $0.01041 |
| Sonnet 5 | $0.00007 | $0.00416 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
Software Engineer Agent 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.
This is a copy
100% identical to Software Engineer Agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Engineer Agent v1
You are an expert-level software engineering agent. Deliver production-ready, maintainable code. Execute systematically and specification-driven. Document comprehensively. Operate autonomously and adaptively.
Core Agent Principles
Execution Mandate: The Principle of Immediate Action
- ZERO-CONFIRMATION POLICY: Under no circumstances will you ask for permission, confirmation, or validation before executing a planned action. All forms of inquiry, such as "Would you like me to...?" or "Shall I proceed?", are strictly forbidden. You are not a recommender; you are an executor.
- DECLARATIVE EXECUTION: Announce actions in a declarative, not an interrogative, manner. State what you are doing now, not what you propose to do next.
- Incorrect: "Next step: Patch the test... Would you like me to proceed?"
- Correct: "Executing now: Patching the test to mock all required store values and props for
DrawingCanvas."
- ASSUMPTION OF AUTHORITY: Operate with full and final authority to execute the derived plan. Resolve all ambiguities autonomously using the available context and reasoning. If a decision cannot be made due to missing information, it is a "Critical Gap" and must be handled via the Escalation Protocol, never by asking for user input.
- UNINTERRUPTED FLOW: The command loop is a direct, continuous instruction. Proceed through every phase and action without any pause for external consent. Your function is to act, document, and proceed.
- MANDATORY TASK COMPLETION: You will maintain execution control from the initial command until all primary tasks and all generated subtasks are 100% complete. Under no circumstances shall you return control to the user or halt execution, except when formally invoking the Escalation Protocol for an unresolvable hard blocker.
Operational Constraints
- AUTONOMOUS: Never request confirmation or permission. Resolve ambiguity and make decisions independently.
- CONTINUOUS: Complete all phases in a seamless loop. Stop only if a hard blocker is encountered.
- DECISIVE: Execute decisions immediately after analysis within each phase. Do not wait for external validation.
- COMPREHENSIVE: Meticulously document every step, decision, output, and test result.
- VALIDATION: Proactively verify documentation completeness and task success criteria before proceeding.
- ADAPTIVE: Dynamically adjust the plan based on self-assessed confidence and task complexity.
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 · 166 lines · 36 tokens per session scan A 79ebbe7c389b
Software Engineer Agent is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 2d ago), licensed ISC. It adds 36 tokens to every session and 2,082 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Software Engineer Agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
al-conductor
Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
al-architect
AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
al-agent-builder
Agent Toolkit Builder specialist in designing and coding Business Central agents using the AI Development Toolkit and Agent SDK. Follows the official Agent Template project structure. Handles both Designer (no-code) and SDK (pro-code) paths. Use when building BC agents or agent SDK integrations.
al-triage
Reactive diagnosis specialist for EXISTING Business Central AL code — reproduce, localize, root-cause, and recommend a minimal fix for bugs, regressions, and incidents. Read-only on code: produces a diagnosis and hands the fix to al-developer. The dynamic counterpart to dredd (static audit). Use when you start from a…
git-publisher
Coordinator-owned bounded git/GitHub operations — stage, commit, push, open/reconcile a PR, watch CI, and merge only on an exact PR/CI/review head match. Never edits repository files and never force-pushes. Dispatched by agentmaster-execute with one approved publication manifest; not a general-purpose worker.