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 randommonicle/claude-skills --skill flag-deferred-itemsgit clone --depth 1 https://github.com/randommonicle/claude-skillsWrote 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/randommonicle/claude-skills/flag-deferred-items)<a href="https://agentmods.dev/skills/randommonicle/claude-skills/flag-deferred-items"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/flag-deferred-items/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/randommonicle/claude-skills/flag-deferred-items"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/flag-deferred-items.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.00075 | $0.00968 |
| Opus 5 | $0.00037 | $0.00484 |
| Sonnet 5 | $0.00015 | $0.00194 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
flag-deferred-items 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 10d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flag deferred items at the anchor
When proposing anything as deferred, do not record it only in a session-specific document and move on. Plant a grep-able flag at the place where the deferred work will actually land.
When this applies
This skill fires whenever a plan, commit, or design discussion contains language like:
- "deferred"
- "out of scope"
- "later commit" / "later phase"
- "future work"
- "future enhancement"
- "Phase N+" / "post-launch" / "post-MVP"
- "not in this PR"
- "follow-up"
Any of those phrases is the trigger. The skill applies regardless of whether the deferral is forced by scope, time, dependency, or design choice.
How to apply
For each deferred item, plant flags at as many of these locations as apply:
-
Code-level anchor. Add a comment at the file, function, or migration the deferred work will touch when it lands. Use a grep-able prefix the project agrees on (commonly
FORWARD:,TODO:, or a project-specific tag). The comment names the deferred item and points at where it was decided.Example:
// FORWARD: spend-cap director-approval queue, see DECISIONS 2026-05-10 -
Migration-level anchor. If a future schema change is anticipated, add a comment in the most recent migration affecting the relevant table family, pointing forward to the expected change.
-
Decision-log entry. Record the deferral in the project's decisions log with a "When this lands, also do X" line so re-reading the entry surfaces secondary work.
-
Handover-note entry. If a handover note is being produced, list deferred items in a dedicated section so the next session sees them on read.
The same item often deserves anchors at multiple locations. A migration deferral typically needs both a comment in the current migration (so the next migration on that table sees it) and a decision-log entry (so re-reading the decision surfaces it).
What "grep-able" means
The anchor must use a literal token consistent enough that grep -rn "<token>" across the codebase returns every deferred item. Inconsistent tokens (TODO in one place, FIXME in another, plain prose in a third) defeat the purpose.
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.
- 10d ago First seen · 67 lines · 75 tokens per session scan A 094fcbec51ca
flag-deferred-items is a skill published in the GitHub repository randommonicle/claude-skills (23 stars, last pushed 3d ago), licensed Apache-2.0. It adds 75 tokens to every session and 968 once invoked, about $0.0004 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…