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 tomzx/agents --skill create-placeholder-issuegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/create-placeholder-issue)<a href="https://agentmods.dev/skills/tomzx/agents/create-placeholder-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-placeholder-issue/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/tomzx/agents/create-placeholder-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-placeholder-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 45 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00116 | $0.02237 |
| Opus 5.5 | $0.00046 | $0.00895 |
| Sonnet 5.5 | $0.00023 | $0.00447 |
| Haiku 4.5 | $0.00012 | $0.00224 |
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 22d 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 — 165 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. ghCLI 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.
Communication guidelines (outbound text)
Before composing any text posted or drafted on the user's behalf, apply communication-guidelines/SKILL.md.
Formatting
- Straight ASCII quotes only, no curly/typographic quotation marks (same rule as
/create-issue).
Steps
-
Resolve the target feature. Use
$1if provided (a feature id likeFEAT-p1, the tokenp1, or a directory namep1-<slug>). Otherwise read.sdlc/state.ymlfeature; if that is unset and exactly onep-prefixed directory exists under.sdlc/features/, use it. If none can be resolved, stop and reportnot-found. -
Locate the feature directory via SDLC_DIR resolution (repo first, then
$SDLC_DIR/{owner}/{repo}/.sdlc/). Record both locations when mirrored. -
Verify it is pending. If the directory token is numeric, the feature is already issue-driven: stop and report
already-issue-drivenwith the issue number from its frontmatter. If the token is notp-prefixed, stop with an error.
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.
- 22d ago Changed · +17 lines c55938f0adeb
- 24d ago Changed 09642c2e2ced
- 27d ago Changed 1a695f1ae5a4
- 28d ago Changed · +4 lines 1e9f44f1a445
- 2mo ago First seen · 144 lines · 116 tokens per session scan A fbbe042f4b05
create-placeholder-issue is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 2,237 once invoked, about $0.0005 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…