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 implementation-comparisongit 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/implementation-comparison)<a href="https://agentmods.dev/skills/smartfrog/opencode-froggy/implementation-comparison"><img src="https://agentmods.dev/badge/skills/smartfrog/opencode-froggy/implementation-comparison/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/implementation-comparison"><img src="https://agentmods.dev/badge/skills/smartfrog/opencode-froggy/implementation-comparison.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.00018 | $0.00273 |
| Opus 5.5 | $0.00007 | $0.00109 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
implementation-comparison 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
Implementation Comparison
Use comparisons when evaluating alternatives is worth the additional cost. Apply the orchestrator's usual validation guidance and coordinate the work through backlog-management.
- Select useful candidates from the configured pool, honoring any models the user explicitly requested. Use separate branches and worktrees at the same starting SHA for a fair comparison. Adjust parallelism to resources and coordination cost.
- Compare candidates against the same acceptance examples and checks. For non-trivial changes, start a fresh
code-reviewersession for this comparison and have it assess every candidate. Share that session only within this comparison, including corrections; another independent comparison gets a new reviewer session. - Choose the candidate that best meets acceptance, manages concrete risks, and avoids unnecessary complexity. Own the selection decision, explain it using evidence, and resolve confirmed blocking review findings.
- Adopt useful parts from another candidate when the benefit justifies the rework, then validate the resulting code and have the same reviewer check substantive changes. Avoid repeated comparisons or polishing that no longer improves the outcome.
- Retain useful alternatives until the selected result is validated. Synchronize and revalidate against newer integration work as needed; clean up discarded workspaces without losing uncommitted work.
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 e3d0b8856dc2
- 14d ago First seen · 15 lines · 18 tokens per session scan A df393e95d5e0
implementation-comparison is a skill published in the GitHub repository smartfrog/opencode-froggy (109 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 273 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-10-11.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…