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 softspark/ai-toolkit --skill autonomous-devgit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/autonomous-dev)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/autonomous-dev"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/autonomous-dev/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.
<a href="https://agentmods.dev/skills/softspark/ai-toolkit/autonomous-dev"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/autonomous-dev.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.02177 |
| Opus 5.5 | $0.00022 | $0.00871 |
| Sonnet 5.5 | $0.00011 | $0.00435 |
| Haiku 4.5 | $0.00005 | $0.00218 |
Grade A, and why
autonomous-dev 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 23d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Development
$ARGUMENTS
Only in Claude Code, apply the model-routing-patterns skill when choosing
executors or creating agent definitions. Delegate to codex:codex-rescue only
when its plugin is installed, enabled and callable in this session. Otherwise
use the installed native agents and their configured models. A context without
the Agent tool returns the dispatch decision to its supervisor; it does not
invent a tool or bypass the client. Preserve explicit user choices and verify
actual completion before accepting a delegated result.
Own one software-delivery run from its requested outcome to a reviewed, verified PR. Continue through reversible decisions within the user's approved scope, recording assumptions where they can be reviewed. Use existing skills for their actual work; this skill owns sequencing, state and the exit gate.
Entry points
| Input | Action |
|---|---|
setup |
Inspect the project and create its validation/tracker/QA configuration |
run <brief, spec path, Jira key, issue URL or PR URL> |
Resolve the task, reuse existing work, then run the process |
list |
List this repository's existing runs without changing state |
resume <run-id> |
Read durable state, claim ownership and continue at the first unmet gate |
status <run-id> |
Read state and report the next action; change nothing |
A plain task description means run. /workflow autonomous-development
routes here. A request only to review code stays with /review; an incident
stays with the incident-response workflow.
Setup and authorization
Read project configuration on first use or when
project commands change. Check the target repository's instructions, KB, actual
build/test commands and provider identities. Keep issueTracker, codeHost and
knowledge separate. For Jira/RAG projects, read the
stack integration contract before discovery
and reuse it for resume, QA and finalization.
What ships with it
7 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.
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.
- 23d ago Changed · +10 lines 8870589ef1b0
- 1mo ago First seen · 177 lines · 54 tokens per session scan A bdc955cef2f9
autonomous-dev is a skill published in the GitHub repository softspark/ai-toolkit (181 stars, last pushed 11d ago), licensed Apache-2.0. It adds 54 tokens to every session and 2,177 once invoked, about $0.0002 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-08.
Other skills, from other repositories
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
load-test
Performance load testing specialist for writing k6/vegeta/wrk scripts, defining SLOs, modeling scenarios (spike/soak/stress/breakpoint), analyzing results, and identifying bottlenecks. ALWAYS use when writing load test scripts, reviewing test results, designing test scenarios, setting performance SLOs, or diagnosing…
e2e-test
Design, maintain, and execute reliable end-to-end tests for critical user journeys with Agent Browser as first choice for exploration and Playwright as the preferred code path for suites and CI. Use for E2E strategy, journey coverage, flaky test triage, artifact collection, CI gating, regression prevention, and…