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/dhar174/custom_github_copilot_agent_builder/software-engineer-agent-v1git clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWhat 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 | $0.00032 | $0.02090 |
| Opus 5 | $0.00016 | $0.01045 |
| Sonnet 5 | $0.00006 | $0.00418 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade A, and why
software-engineer-agent-v1 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- software-engineer-agent-v1 — 98% identical, 32 lines differ
How it starts
The opening of the file, as written. The whole thing — 193 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 · 193 lines · 32 tokens per session scan A 6052fd482d9b
software-engineer-agent-v1 is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 2,090 once invoked, about $0.0002 per session on Opus 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
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.