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/arindam200/awesome-ai-apps/software-engineergit clone --depth 1 https://github.com/Arindam200/awesome-ai-appsWrote 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/arindam200/awesome-ai-apps/software-engineer)<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="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 | $0.00098 | $0.02953 |
| Opus 5 | $0.00049 | $0.01477 |
| Sonnet 5 | $0.00020 | $0.00591 |
| Haiku 4.5 | $0.00010 | $0.00295 |
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 4d 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). Copies of this mod
1 near-identical copy found in the catalogue:
- software-engineer — 98% identical, 6 lines differ
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
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).- 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, orlogic). - (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.
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.
- 4d ago First seen · 218 lines · 98 tokens per session scan B 3b6669be4b0b
software-engineer is an agent published in the GitHub repository Arindam200/awesome-ai-apps (13,571 stars, last pushed 4d ago), licensed MIT. It adds 98 tokens to every session and 2,953 once invoked, about $0.0005 per session on Opus 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.
Other agents, from other repositories
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
AEM Front-End Specialist
Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration.
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…