software-engineer

software-engineer is an agent for Claude Code from Arindam200/awesome-ai-apps. It costs 98 tokens per session (2,953 once invoked), scanned B, original, MIT.

A software-engineer role that implements one prepared workshop task in the project’s source code. It follows the task’s requirements and hands the result to a tester.

In plain words
What is it for?
Use it to turn a groomed task into code, run the required QA and end-to-end checks, and prepare an implementation hand-off.
Why use it?
It gives the coding phase a defined scope and checklist, including the project’s formatting, linting, and end-to-end checks.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents); mentions AGENTS.md.

Good fit Use it to turn a groomed task into code, run the required QA and end-to-end checks, and prepare an implementation hand-off.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/arindam200/awesome-ai-apps/software-engineer
About the project

Awesome AI Apps is a collection of 132 projects, tutorials, and recipes for building applications powered by large language models. Developers use it to explore text and voice agents, retrieval-augmented generation, workflows, MCP tools, memory, and fine-tuning.

Arindam200/awesome-ai-apps · 16,424 stars · on GitHub · dub.sh

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/Arindam200/awesome-ai-apps

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

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/arindam200/awesome-ai-apps/software-engineer"><img src="https://agentmods.dev/badge/agents/arindam200/awesome-ai-apps/software-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 98 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,953 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00098 $0.02953
Opus 5.5 $0.00039 $0.01181
Sonnet 5.5 $0.00020 $0.00591
Haiku 4.5 $0.00010 $0.00295

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

Security

Grade B, and why

software-engineer scanned grade B with 1 finding 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

- AC3: PASS — evidence: `ls implement_yourself/.claude/skills/foo/SKILL.md` returned a real path; YAML frontmatter parses (`uv run python -c "import yaml; yaml.safe_load(...)"` → no error).
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

advance_ai_agents/deep_research_writing_agents_nebius_okahu/implement_yourself/.agents/skills/implement-universal/agents/software-engineer.md · 218 lines

How it starts

The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Software Engineer Role — Workshop Edition (Universal)

This file is loaded as a role definition by /implement-universal's orchestrator at the start of the SWE phase. Read it end-to-end before writing any code in the SWE phase — your default coding instinct is overridden by what this file says.

You implement one pre-groomed ticket from implement_yourself/tasks/. The ticket has full Scope, Acceptance Criteria, and User Stories — your job is to translate that into code that passes both the QA targets and (on logic tickets) the Tester phase's adversarial pass.

Always read first

  1. implement_yourself/CLAUDE.md — the project context, structure, tech stack (Pydantic + Pydantic Settings + FastMCP + Click + Nebius via LangChain, Exa, Gemini image generation, and Okahu/Monocle tracing), QA conventions (make format-fix, make lint-fix, make format-check, make lint-check), and run conventions (everything routed through Make + uv).
  2. The ticket file itself — every line. Pay special attention to:
    • The Scope section (file paths, public interfaces, signatures).
    • The Acceptance Criteria (your contract with the Tester phase).
    • The User Stories (used to drive the e2e adversarial pass).
    • Notes (constraints, things to avoid, future-task references).

Input

The orchestrator hands you (in the SKILL.md step-4 instructions):

  • The ticket path (e.g. implement_yourself/tasks/003-implement-analyze-youtube-video.groomed.md).
  • The working directory (implement_yourself/).
  • The list of immutable scaffolding files.
  • The ticket archetype (docs, glue, or logic).
  • (On re-entry after a Tester FAIL) Concrete feedback from the Tester phase.

Workflow

Step 1 — Read the ticket end-to-end

Map every Acceptance Criterion to one or more concrete file changes. Make a private list (your harness's task tool, or notes in the chat) so nothing is forgotten.

If anything in the spec is genuinely ambiguous (multiple plausible interfaces, contradictory ACs), stop and escalate. Do not guess — surface the question to the human running the orchestrator.

Read the full file on GitHub · 218 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 · 218 lines · 98 tokens per session scan B 3b6669be4b0b

Subscribe to this mod's changes

software-engineer is an agent published in the GitHub repository Arindam200/awesome-ai-apps (16,424 stars, last pushed 11d ago), licensed MIT. It adds 98 tokens to every session and 2,953 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.