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 backlog-managementgit 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/backlog-management)<a href="https://agentmods.dev/skills/smartfrog/opencode-froggy/backlog-management"><img src="https://agentmods.dev/badge/skills/smartfrog/opencode-froggy/backlog-management/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/backlog-management"><img src="https://agentmods.dev/badge/skills/smartfrog/opencode-froggy/backlog-management.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.00023 | $0.01178 |
| Opus 5.5 | $0.00009 | $0.00471 |
| Sonnet 5.5 | $0.00005 | $0.00236 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade A, and why
backlog-management 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 today.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Management
Use tracking to coordinate, resume and verify delivery, not as an approval queue. Create only tasks with a coherent outcome; do not create a ticket for every worker, test or trial.
Source of truth
Use one authoritative backlog. By default use task-board in the canonical project's .opencode/memory/memory.db, shared across its worktrees. Do not maintain a parallel Markdown backlog or coordination journal as live state. Existing Markdown files are not automatically imported or deleted; agree a migration before changing their authority.
If Linear or Trello is explicitly requested, discover its actual MCP tools, destinations, statuses and members before writing. An unresolved destination blocks publication, not independently actionable work. Do not silently replace an external tracker with local state or synchronize two authoritative backlogs. External trackers retain their established ownership rules.
Simple tasks
Each task has an ID, title, status and detailed Markdown description. Statuses are todo, in-progress, blocked, review, done.
Keep scope, observable acceptance, established state, blocker, next action and necessary evidence/recovery links in one coherent current description. Include worker/session/workspace references when needed to resume. Keep title, status and description consistent by replacing obsolete sections, not appending each transition. There are no task notes, update feeds or history sections. Detailed trials stay in linked reports; do not generate reports merely to relocate redundant prose. Dispatch is not proof of execution; an experiment or static check does not establish product acceptance.
Search before creating, preserve IDs and concurrent work, and verify writes. Narrow discovery with a status, topic or query. Read full affected records before replacing content and use the returned version for updates. If rendering is truncated, obtain the missing text through an authorized path; if it remains unread or inaccessible, stop that replacement and report incomplete coverage. Excerpts and summaries do not substitute for the full record.
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.
- today Changed 3e22a8d4b60f
- 6d ago Changed f9cc45f752dd
- 7d ago Changed · -25 lines · +1 tokens per session f126df6b378c
- 10d ago Changed · +4 lines 61abcd2bd915
- 11d ago Changed · +2 lines 396b73bc9cb1
- 14d ago Changed · -13 lines · -1 tokens per session 1acd2ab39f9f
- 26d ago First seen · 83 lines · 23 tokens per session scan A 718ba59154fc
backlog-management is a skill published in the GitHub repository smartfrog/opencode-froggy (109 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,178 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…