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.
git clone --depth 1 https://github.com/SebastienDegodez/skraft-pluginWrote 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/agents/sebastiendegodez/skraft-plugin/software-engineer)<a href="https://agentmods.dev/agents/sebastiendegodez/skraft-plugin/software-engineer"><img src="https://agentmods.dev/badge/agents/sebastiendegodez/skraft-plugin/software-engineer/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/agents/sebastiendegodez/skraft-plugin/software-engineer"><img src="https://agentmods.dev/badge/agents/sebastiendegodez/skraft-plugin/software-engineer.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.00064 | $0.04852 |
| Opus 5.5 | $0.00026 | $0.01941 |
| Sonnet 5.5 | $0.00013 | $0.00970 |
| Haiku 4.5 | $0.00006 | $0.00485 |
Grade A, and why
software-engineer 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 9d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 9d ago Changed · +4 lines 9dfdb7f98656
- 10d ago Changed · +7 lines 6263c2240cb4
- 11d ago Changed · +6 lines 3ad0418fd202
- 16d ago Changed · +35 lines 87344bbd229a
- 20d ago Changed · +3 lines 756be7b207f0
- 23d ago Changed · +10 lines · -2 tokens per session 7d4614128eff
- 1mo ago Changed · +104 lines · +66 tokens per session dfec875d026c
- 1mo ago First seen · 68 lines · 0 tokens per session scan A d212a005d1ac
software-engineer is an agent published in the GitHub repository SebastienDegodez/skraft-plugin (12 stars, last pushed today), licensed GPL-3.0. It adds 64 tokens to every session and 4,852 once invoked, about $0.0003 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 agents, from other repositories
swift-reviewer
Independent verifier for Swift/iOS changes. Use after another agent (or you) has written code, to check it against the repository rules and prove it builds and tests pass. Runs builds and tests and returns their real output. Read-only — it holds no write tools, so it cannot fix what it should report, and it never…
testing-expert
Read-only testing reviewer. Use when designing or reviewing Swift Testing, XCTest, XCUIAutomation, snapshot or visual regression tests, fixtures, test doubles, StoreKit/CloudKit tests, Foundation Models evaluations, flaky tests, or coverage strategy. Reports recommendations and does not edit code.
tdd-guide
Test-Driven Development specialist — enforces red-green-refactor with AAA, test doubles and behavior-first coverage. Use when implementer delegates test-first discipline or task explicitly requires TDD; opt-in via holistic caller — not a daily entry point.
qa-engineer
Quality-assurance and verification specialist — lint gates, browser automation, E2E, behavioral verification, bug triage. Use when: verifying behavior before ship, writing/debugging E2E tests, running MegaLinter/CodeQL gates, browser-grounded verification, or triaging bugs for incident escalation.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.