software-engineering

software-engineering is a skill for Claude Code, Codex from atstaeff/ai-agents. It costs 20 tokens per session (201 once invoked), scanned A, original, MIT.

A set of everyday practices for writing, reviewing, testing, and improving software so it stays understandable and maintainable.

In plain words
What is it for?
Use it when creating or reviewing code, choosing design patterns, applying SOLID principles, planning tests, or refactoring existing software.
Why use it?
It helps prevent messy code, unsafe changes, unclear designs, and weak tests from becoming harder to fix later.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when creating or reviewing code, choosing design patterns, applying SOLID principles, planning tests, or refactoring existing software.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atstaeff/ai-agents/software-engineering
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.

Any agent
npx skills add atstaeff/ai-agents --skill software-engineering
Clone the repo
git clone --depth 1 https://github.com/atstaeff/ai-agents

Made for: Claude Code, Codex.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/atstaeff/ai-agents/software-engineering"><img src="https://agentmods.dev/badge/skills/atstaeff/ai-agents/software-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 201 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.00020 $0.00201
Opus 5.5 $0.00008 $0.00080
Sonnet 5.5 $0.00004 $0.00040
Haiku 4.5 $0.00002 $0.00020

Measured 12d ago against content hash 277b67d34d0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

software-engineering 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 12d 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.

skills/software-engineering/SKILL.md · 26 lines

What it actually says

Software Engineering

Workflow

  1. Understand the required behavior and the existing code before proposing structural changes.
  2. Load clean-code, code-review, testing-strategies, practical-refactoring, solid-principles or design-patterns only as needed.
  3. Prefer a small verified change; make abstractions earn their place and document only consequential choices.

Completion

Return the concrete result, verification evidence and any material unresolved limitation. Keep documentation proportional to the change and preserve human feedback.

Select a focused topic

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. 12d ago Changed · -8 tokens per session 277b67d34d0d
  2. 1mo ago First seen · 26 lines · 28 tokens per session scan A bc24e9e3c9d2

Subscribe to this mod's changes

software-engineering is a skill published in the GitHub repository atstaeff/ai-agents (3 stars, last pushed 10d ago), licensed MIT. It adds 20 tokens to every session and 201 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-08-31.

Related

Other skills, from other repositories

adk-go-self-review

Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…

google/adk-go · 87 tokens

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…

emdash-cms/emdash · 72 tokens

go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

Gentleman-Programming/gentle-ai · 26 tokens

semgrep-rule-variant-creator

Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.

waybarrios/opencode-power-pack · 50 tokens

brooks-sweep

Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…

hyhmrright/brooks-lint · 178 tokens

plugin-review

Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.

athola/claude-night-market · 23 tokens