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 smartfrog/opencode-froggy --skill extreme-programminggit clone --depth 1 https://github.com/smartfrog/opencode-froggyWrote 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/smartfrog/opencode-froggy/extreme-programming)<a href="https://agentmods.dev/skills/smartfrog/opencode-froggy/extreme-programming"><img src="https://agentmods.dev/badge/skills/smartfrog/opencode-froggy/extreme-programming/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/smartfrog/opencode-froggy/extreme-programming"><img src="https://agentmods.dev/badge/skills/smartfrog/opencode-froggy/extreme-programming.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.00022 | $0.00275 |
| Opus 5.5 | $0.00009 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
extreme-programming 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 11d 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
Extreme Programming
- Communication: share objectives, acceptance examples, relevant context, and evidence so another agent can resume the work.
- Simplicity: apply KISS and YAGNI; reuse existing capabilities and evolve the simplest design meeting current needs.
- Feedback: verify assumptions early, integrate validated changes frequently, and adjust product decisions using actual user feedback. Use
tddfor implementation andbacklog-managementfor ticket workflow. - Courage: report failed checks and uncertainty honestly; revise decisions when evidence changes.
- Respect: give specific, evidence-based feedback, preserve others' work, and bound investigation and correction costs.
Implementers own tests and ongoing refactoring. Before integrating or completing a non-trivial change set, the coordinator obtains an independent code-reviewer review, including for changes to behavior, configuration, or agent instructions. Passing tests or implementer self-review do not replace it. Trivial typos and formatting-only changes may use direct checks. Simplifiers provide targeted help.
Follow shared project conventions; temporary scopes coordinate edits rather than establish permanent code ownership. A passing isolated branch is not proof of successful integration. Prefer reversible design decisions and distinguish production-ready changes from experimental findings.
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.
- 11d ago Changed · +2 lines 35d2f2a095ed
- 26d ago First seen · 15 lines · 22 tokens per session scan A 7cd4c1e1c353
extreme-programming is a skill published in the GitHub repository smartfrog/opencode-froggy (109 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 275 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-09-29.
Other skills, from other repositories
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.
product
Consolidated Galyarder Framework Product intelligence bundle.
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
create-issues
Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.