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 skills add avatsaev/av-swe-skill --skill av-swegit clone --depth 1 https://github.com/avatsaev/av-swe-skillWrote 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/skills/avatsaev/av-swe-skill/av-swe)<a href="https://agentmods.dev/skills/avatsaev/av-swe-skill/av-swe"><img src="https://agentmods.dev/badge/skills/avatsaev/av-swe-skill/av-swe.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.1 | $0.00166 | $0.01589 |
| Opus 5 | $0.00083 | $0.00794 |
| Sonnet 5 | $0.00033 | $0.00318 |
| Haiku 4.5 | $0.00017 | $0.00159 |
Grade A, and why
av-swe 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AV-SWE — plan-driven software engineering at scale
Turn a large software engineering effort into a small, ordered, dependency-aware, verifiable task
plan, and execute it reliably. Built by generalizing the clean-room
scope → plan → implement skills for ordinary development where the real source code is present
(no clean-room blinders), plus explicit long-lived project-management operations for driving a big
project over many sessions.
The whole system lives under a plan root (default <project-root>/swe/) and is driven by seven
operations (block/unblock are two directions of one mechanism). Nothing here is a rigid process
for its own sake — the point is that a big project stays plannable, trackable, and consistently
deliverable without the plan rotting.
This file is deliberately a thin index. Each op's full procedure lives in its own file under ops/;
shared conventions (layout, naming, state machine, config schema) live under conventions/. Read the
linked file for the op you're about to run — do not rely on this page alone.
When to use
- The user wants to plan a large project, feature set, migration, or refactor.
- The user wants to break a large body of work into sprints and small atomic tasks.
- The user wants to execute a planned chunk of work with confidence it actually builds and verifies.
- The user asks "where are we", "what's next", "is the plan consistent", or wants to move tasks between states.
Operations at a glance
| Op | Effect | Produces / mutates | Full procedure |
|---|---|---|---|
av-swe scope |
Capture requirements and current architecture into spec docs | swe/specs/*.md |
ops/scope.md |
av-swe plan |
Derive an ordered sprint + task plan from specs/source | swe/PLAN.md, swe/sprint-NNN-*/ |
ops/plan.md |
av-swe implement |
Execute one sprint through the state machine, gated on build+test | task moves + *-summary.md |
ops/implement.md |
av-swe status |
Report plan health: open/in_progress/blocked/done, next sprint, gaps | read-only report | ops/status.md |
av-swe validate |
Check plan integrity (ordering, deps, coverage, ids) | read-only report | ops/validate.md |
av-swe block / unblock |
Move a task to/from the blocked state | task file moves | ops/block-unblock.md |
av-swe configure |
Inspect or set project conventions | swe/av-swe.config.json |
ops/configure.md |
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- conventions/config.md 2.1 KB
- conventions/layout.md 3.1 KB
- ops/block-unblock.md 496 B
- ops/configure.md 308 B
- ops/implement.md 2.8 KB
- ops/plan.md 3.0 KB
- ops/scope.md 2.1 KB
- ops/status.md 483 B
- ops/validate.md 809 B
- references/plan-template.md 1.7 KB
- references/spec-overview-template.md 1.8 KB
- references/spec-sub-template.md 1.6 KB
- references/summary-template.md 1.2 KB
- references/task-template.md 2.2 KB
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.
- 8d ago First seen · 101 lines · 166 tokens per session scan A dfd27dfc0505
av-swe is a skill published in the GitHub repository avatsaev/av-swe-skill (4 stars, last pushed 19d ago), licensed MIT. It adds 166 tokens to every session and 1,589 once invoked, about $0.0008 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 skills, from other repositories
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.
github-triage
Unified GitHub triage for issues AND PRs. Classifies open items, answers questions from codebase, analyzes bugs, reviews PRs, and produces a structured triage report. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
issue-report-generator
Automatically generate clear, actionable issue reports from failing tests and repository analysis. Analyze test failures to understand expected vs. actual behavior, identify affected code components, and produce well-structured Markdown reports suitable for GitHub Issues or similar trackers. Use when a test fails…
python-repo-quickstart
Quickly analyzes Python repositories to understand their purpose, structure, and setup requirements. Use when Claude needs to onboard to a new Python codebase, understand project structure, identify entry points, determine dependencies, or generate setup instructions. Trigger when users ask to "analyze this Python…
backlog
EXPERIMENTAL. Use when working the project-wide out-of-scope backlog at paad/code-reviews/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is /agentic-review — and not for reviewing a branch diff.
openase-platform
Platform operations for tickets, projects, and runtime coordination inside OpenASE.