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 rysh-ai/rysh-cli-code --skill softdev-loopgit clone --depth 1 https://github.com/rysh-ai/rysh-cli-codeWrote 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/rysh-ai/rysh-cli-code/softdev-loop)<a href="https://agentmods.dev/skills/rysh-ai/rysh-cli-code/softdev-loop"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/softdev-loop/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/rysh-ai/rysh-cli-code/softdev-loop"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/softdev-loop.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.00015 | $0.00406 |
| Opus 5.5 | $0.00006 | $0.00162 |
| Sonnet 5.5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
softdev-loop 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 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.
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.
What it actually says
You run one pass of a Go software-development loop in {{workdir}}, working toward: {{goal}}
The pass
- Orient. Read the code the goal touches before writing any. Follow the project's existing conventions — file layout, error style, test style.
- Implement the smallest honest slice of the goal.
- Test. Every behaviour you add gets a test that fails without it. Run
go test ./...— the whole module, not just your package. - Vet. Run
go vet ./...and fix what it reports.
Rules
- Never weaken or delete an existing test to get green.
- Never commit or push — the loop produces a working tree; the human reviews and commits.
- If the goal is ambiguous, implement the narrow reading and say in your report which reading you chose and why.
- End every pass by reporting: what changed, what is verified green, and what (if anything) remains for the next pass.
What ships with it
3 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.
- 1mo ago First seen · 46 lines · 15 tokens per session scan A 18c9f43448f0
softdev-loop is a skill published in the GitHub repository rysh-ai/rysh-cli-code (5 stars, last pushed 11d ago), licensed Apache-2.0. It adds 15 tokens to every session and 406 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.
Other skills, from other repositories
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
vite-plus-conventions
vite+ unified TypeScript toolchain conventions: the vp CLI for package/node management, oxlint/oxfmt, type-aware linting, vitest, rolldown/tsdown bundling, task caching, and migration. Load when configuring or reviewing a vite+ TypeScript toolchain.