Software Engineer Agent

Software Engineer Agent is an agent for Claude Code from github/awesome-copilot. It costs 36 tokens per session (2,082 once invoked), scanned A, original, MIT.

A software development agent that follows specifications to build, document, and maintain production-ready code.

In plain words
What is it for?
Use it for implementing features, fixing code, documenting systems, and handling development tasks across a project.
Why use it?
It provides a structured way to carry out engineering work and keep the resulting code maintainable.

Agent for Claude Code ✓ vendor

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it for implementing features, fixing code, documenting systems, and handling development tasks across a project.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/github/awesome-copilot/software-engineer-agent-v1
About the project

Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.

github/awesome-copilot · 40,285 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/github/awesome-copilot

Made for: Claude Code.

Wrote 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.

agentmods badge for Software Engineer Agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/github/awesome-copilot/software-engineer-agent-v1/github.svg)](https://agentmods.dev/agents/github/awesome-copilot/software-engineer-agent-v1)
Your own site
<a href="https://agentmods.dev/agents/github/awesome-copilot/software-engineer-agent-v1"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/software-engineer-agent-v1/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.

agentmods 80×15 button for Software Engineer Agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/github/awesome-copilot/software-engineer-agent-v1"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/software-engineer-agent-v1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,082 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.02082
Opus 5.5 $0.00014 $0.00833
Sonnet 5.5 $0.00007 $0.00416
Haiku 4.5 $0.00004 $0.00208

Measured 1mo ago against content hash 79ebbe7c389b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

agents/software-engineer-agent-v1.agent.md · 166 lines

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.

Read the full file on GitHub · 166 lines

Changes

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.

  1. 1mo ago First seen · 166 lines · 36 tokens per session scan A 79ebbe7c389b

Subscribe to this mod's changes

Software Engineer Agent is an agent published in the GitHub repository github/awesome-copilot (40,285 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 2,082 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.

Related

Other agents, from other repositories

apm-expert

Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.

microsoft/apm · 39 tokens

ndv-tester

Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.

emb715/neurodiveragents · 54 tokens

ndv-diagnose

Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything broken that needs a root cause — not a guess. Locks onto the problem and will not stop until the cause is confirmed, not just located.

emb715/neurodiveragents · 57 tokens

ndv-refactor

Code transformation specialist. Use when renaming, extracting, restructuring, or modernizing syntax. OCD form — incorrect structure is not a style preference, it is an intolerable state that must be corrected incrementally and completely.

emb715/neurodiveragents · 49 tokens

ndv-review

Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.

emb715/neurodiveragents · 50 tokens

ndv-research

Codebase research specialist. Use when the question is "where is X", "how does Y work", "trace this flow", "what files are involved in Z", or any investigation that requires reading across multiple files and synthesizing a clear answer. Hyperlexic pattern recognition — builds a complete map before synthesizing, finds…

emb715/neurodiveragents · 85 tokens