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 commands/insight-services-apac/ingenious/create-specgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/commands/insight-services-apac/ingenious/create-spec)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/create-spec"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/create-spec.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.00000 | $0.00069 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
create-spec 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 yesterday.
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.
What it actually says
write a comprehensive file in markdown listing down comprehensive user stories to for an agent to test. name this file spec.md. Focus only on user stories that can be tested with Playwright MCP. Make sure to document all existing features in the app found in the codebase. DO NOT add any user stories that are not found in this codebase.
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.
- yesterday First seen · 2 lines · 0 tokens per session scan A b7cac5c2d4d2
create-spec is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 69 tokens. 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-09-04.
Other commands, from other repositories
run-test
Execute AI agent test script in real browser.
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
test-write
Write a new Playwright E2E test using the discovery-first workflow.
naive-test
Drive the live app as a naive first-time user and report UX/behavior gaps before deploy.
resume-ai-validator
端到端验证 resumeAI 的 API 能力和 UI/UX 交互的 CLI 工具。.