Monstrare: Skill for Claude Code

.claude/skills/spec-interrogation/SKILL.md

spec-interrogation is a skill for Claude Code from pjwang2022/Monstrare. It costs 47 tokens per session (85 once invoked), scanned A, original, MIT.

A requirements-review workflow that turns vague feature requests into a written specification. The specification lists requirements, exclusions, edge cases, and acceptance criteria for human review.

In plain words
What is it for?
Use it when a feature request is incomplete or ambiguous and needs a precise, reviewable definition of scope and expected behavior.
Why use it?
It exposes missing details and unclear boundaries before implementation begins, reducing misunderstandings about what should be built.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code; mentions Codex.

This is pjwang2022/Monstrare's own configuration. It tells Claude Code how to work on Monstrare itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Monstrare configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pjwang2022/Monstrare. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pjwang2022/Monstrare/main/.claude/skills/spec-interrogation/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/pjwang2022/Monstrare

Made for: Claude Code.

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 spec-interrogation

README.md
[![agentmods](https://agentmods.dev/badge/skills/pjwang2022/monstrare/spec-interrogation.svg)](https://agentmods.dev/skills/pjwang2022/monstrare/spec-interrogation)
Your own site
<a href="https://agentmods.dev/skills/pjwang2022/monstrare/spec-interrogation"><img src="https://agentmods.dev/badge/skills/pjwang2022/monstrare/spec-interrogation.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 85 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00047 $0.00085
Opus 5 $0.00023 $0.00043
Sonnet 5 $0.00009 $0.00017
Haiku 4.5 $0.00005 $0.00009

Measured 8d ago against content hash 1ed254b8c586, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

spec-interrogation 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 8d 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.

.claude/skills/spec-interrogation/SKILL.md · 7 lines

What it actually says

請閱讀並遵循 ai/skills/spec-interrogation.md(此為 Claude Code 與 Codex 共用的正本內容)。

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. 8d ago First seen · 7 lines · 47 tokens per session scan A 1ed254b8c586

Subscribe to this mod's changes

spec-interrogation is a skill published in the GitHub repository pjwang2022/Monstrare (86 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 85 once invoked, about $0.0002 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-30.

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