agentmods.dev

create-placeholder-issue

create-placeholder-issue is a skill for Claude Code, Codex from tomzx/agents. It costs 116 tokens per session (2,178 once invoked), scanned A, original, MIT.

A workflow for promoting a pending software feature into an issue-tracked feature by creating a placeholder GitHub issue. It renames the feature directory and updates its internal references to use the new issue number.

In plain words
What is it for?
Creating a minimal issue for a pending feature directory and converting `FEAT-p...` references to the corresponding issue-driven form.
Why use it?
It connects work that started without a GitHub issue to the project's normal issue-based tracking system.

Skill for Claude CodeCodex

not rated 6 +1 yesterday A scan 116 tokens original MIT
View the source file tomzx/agents
Install

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.

agentmods
npx agentmods add skills/tomzx/agents/create-placeholder-issue
Any agent
npx skills add tomzx/agents --skill create-placeholder-issue
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for create-placeholder-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/create-placeholder-issue.svg)](https://agentmods.dev/skills/tomzx/agents/create-placeholder-issue)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/create-placeholder-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-placeholder-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00116 $0.02178
Opus 5 $0.00058 $0.01089
Sonnet 5 $0.00023 $0.00436
Haiku 4.5 $0.00012 $0.00218

Measured 5d ago against content hash fbbe042f4b05, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

create-placeholder-issue 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 5d 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.

skills/create-placeholder-issue/SKILL.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Placeholder Issue

Creates a minimal placeholder GitHub issue for a pending SDLC feature, then promotes the feature to issue-driven form: renames the directory to the new issue number and rewrites every FEAT-p<seq> cross-reference to FEAT-<issue>.

This is the promotion step defined by the Feature Directory Naming convention in skills/sdlc/references/shared.md. Use it for features created bottom-up (e.g. by sync-sdlc from code analysis) that have no GitHub issue yet. For top-down work where you start from a feature request, use /create-issue, which produces a full structured issue.

Prerequisites

  • Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
  • gh CLI authenticated with write access to create issues in the target repository.
  • A pending feature directory p<seq>-<slug> under .sdlc/features/ (resolved via SDLC_DIR if set).

Skill attribution (GitHub)

Before creating the issue, read github-post-attribution/SKILL.md and append the Created with footer for SKILL_DIR = create-placeholder-issue to the issue body.

Formatting

  • Straight ASCII quotes only, no curly/typographic quotation marks (same rule as /create-issue).

Steps

  1. Resolve the target feature. Use $1 if provided (a feature id like FEAT-p1, the token p1, or a directory name p1-<slug>). Otherwise read .sdlc/state.yml feature; if that is unset and exactly one p-prefixed directory exists under .sdlc/features/, use it. If none can be resolved, stop and report not-found.

  2. Locate the feature directory via SDLC_DIR resolution (repo first, then $SDLC_DIR/{owner}/{repo}/.sdlc/). Record both locations when mirrored.

  3. Verify it is pending. If the directory token is numeric, the feature is already issue-driven: stop and report already-issue-driven with the issue number from its frontmatter. If the token is not p-prefixed, stop with an error.

  4. Duplicate check. Read the feature's frontmatter issue field; if it is already set, treat the feature as already promoted (already-issue-driven). Otherwise search for an existing open issue mentioning the feature slug and "placeholder":

    gh issue list --search "<slug> placeholder" --state open --limit 10

    If one is found that was produced by this skill, reuse its number M and skip to step 7 (rename), linking the existing issue instead of creating a duplicate.

Read the full file on GitHub · 144 lines

Changes

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.

  1. 5d ago First seen · 144 lines · 116 tokens per session scan A fbbe042f4b05

Subscribe to this mod's changes

create-placeholder-issue is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 2,178 once invoked, about $0.0006 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.

Git and workflowProject management
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens