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 mataeil/OODA-loop --skill plan-backloggit clone --depth 1 https://github.com/mataeil/OODA-loopWrote 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/mataeil/ooda-loop/plan-backlog)<a href="https://agentmods.dev/skills/mataeil/ooda-loop/plan-backlog"><img src="https://agentmods.dev/badge/skills/mataeil/ooda-loop/plan-backlog/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/mataeil/ooda-loop/plan-backlog"><img src="https://agentmods.dev/badge/skills/mataeil/ooda-loop/plan-backlog.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.00040 | $0.01998 |
| Opus 5.5 | $0.00016 | $0.00799 |
| Sonnet 5.5 | $0.00008 | $0.00400 |
| Haiku 4.5 | $0.00004 | $0.00200 |
Grade A, and why
plan-backlog 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-backlog: GitHub Issues RICE Scorer
Fetches open GitHub Issues, scores each with RICE (Reach × Impact × Confidence ÷ Effort),
and outputs a ranked priority table. READ-ONLY — writes only to agent/state/backlog.json.
Step 0: Safety
HALT check — if config.safety.halt_file exists: print [HALT] plan-backlog stopped. Reason: {content} and exit.
gh check — run gh --version. If unavailable:
gh CLI not available. Skipping plan-backlog.
Install: https://cli.github.com | Auth: gh auth login
Exit cleanly (not an error).
Step 1: Load Issues
Remote check — before fetching issues, verify a GitHub remote exists:
git remote -v 2>/dev/null | grep -qE 'github\.com[:/]'
This checks for any remote pointing to GitHub (regardless of remote name — origin,
upstream, etc.) and rejects non-GitHub remotes (GitLab, Bitbucket, etc.) that would
cause gh to fail with a confusing error.
If no GitHub remote is found:
- Print
[plan-backlog] No GitHub remote configured. Backlog scoring requires a GitHub repository with issues. Skipping. - Write state file with
"status": "no_remote"(preserve and incrementrun_countif state already exists) - Exit 0 — do NOT crash or show raw git errors
EVERY early-exit state write (no_remote, no_issues, fetch/parse error) MUST
also include "actionable_items": 0, "top_rice_score": 0.0 — evolve's 4-B chain
trigger evaluates those fields (actionable_items >= 1 AND top_rice_score >= 50);
omitting them leaves the condition undecidable instead of cleanly false.
gh issue list --state open --json number,title,labels,body,createdAt,assignees --limit 100
On command error → Could not fetch issues. Is this a GitHub repository? Skipping. — exit 0.
On malformed JSON (parse error) → treat identically to command error: log Could not parse gh output. Skipping. — exit 0.
On empty array → write state with status: "no_issues", print No open issues to score. — exit 0.
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.
- 2mo ago First seen · 180 lines · 40 tokens per session scan A ac2739bffa0c
plan-backlog is a skill published in the GitHub repository mataeil/OODA-loop (6 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,998 once invoked, about $0.0002 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
principle-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.