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 agentmods add skills/kangminhyuk1111/agents/spec-interviewnpx skills add kangminhyuk1111/agents --skill spec-interviewgit clone --depth 1 https://github.com/kangminhyuk1111/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/kangminhyuk1111/agents/spec-interview)<a href="https://agentmods.dev/skills/kangminhyuk1111/agents/spec-interview"><img src="https://agentmods.dev/badge/skills/kangminhyuk1111/agents/spec-interview.svg" alt="Measured on agentmods" 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.00052 | $0.01784 |
| Opus 5 | $0.00026 | $0.00892 |
| Sonnet 5 | $0.00010 | $0.00357 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
spec-interview 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 170 lines · 52 tokens per session scan A 796fd9fdc62d
spec-interview is a skill published in the GitHub repository kangminhyuk1111/agents (2 stars, last pushed 7mo ago), with no licence file. It adds 52 tokens to every session and 1,784 once invoked, about $0.0003 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
codex-auth-setup
Install or refresh codex-multi-auth for the official Codex CLI, run first login, and verify account health and routing.
codexu-release
Run this skill from the repository root. Treat the release as a real public publish: verify the current remote state first, keep unrelated user changes out of release commits, and report exactly what was built, pushed, and released.
codexu-pr-review
Review codexU pull requests and decide whether they should be merged, changed, split, declined, or kept as a fork based on product positioning, roadmap, privacy, data semantics, native macOS design, architecture, scope, and verification. Use for PR review, mergeability assessment, contribution triage, and feature-fit…
example
Example fixture skill for scanner regression coverage.
context-canvas-checkpoint
Maintain an optional session task map and explicit retrievable references in Context Canvas Codex. Use when navigation or long-context offload would materially help with goals, decisions, progress, dependencies, blockers, next steps, exploration summaries, large textual tool results, or selective historical…
context-canvas-reflection
Run one bounded trajectory reflection when repeated same-cause failures, contradicted assumptions, real-use failure after local green, material scope drift, a materially unresolved phase boundary, an unapproved authority-sensitive next effect, or user doubt suggests the current path may be wrong. Use Context Canvas…