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 LIDR-academy/lidr-specboot --skill show-spec-workinggit clone --depth 1 https://github.com/LIDR-academy/lidr-specbootWrote 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/lidr-academy/lidr-specboot/show-spec-working)<a href="https://agentmods.dev/skills/lidr-academy/lidr-specboot/show-spec-working"><img src="https://agentmods.dev/badge/skills/lidr-academy/lidr-specboot/show-spec-working/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/lidr-academy/lidr-specboot/show-spec-working"><img src="https://agentmods.dev/badge/skills/lidr-academy/lidr-specboot/show-spec-working.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00995 |
| Opus 5 | $0.00022 | $0.00498 |
| Sonnet 5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
show-spec-working scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Execute curl command(s) that show real response behavior. How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
show-spec-working Skill
Demonstrate a spec in a runnable way.
If the user does not provide explicit context, use the spec/change currently being worked on in this session.
Always end by reporting completion in chat.
Trigger phrases (high priority)
Treat these expressions as execution commands, not analysis requests:
show me Xdemo Xwalk me through Xshow X workinghow X worksprove X works
When any of these appear, run the demonstration workflow directly. Do not stop at a feature summary or quick report.
Inputs
- Optional spec context from user:
- Direct ticket id in text (for example:
SCRUM-10) - Feature name
- Endpoint
- Frontend route
- Direct ticket id in text (for example:
- If missing, infer from current session context and currently active work.
Workflow
Step 1 - Resolve target spec and scope
- Identify the target spec/change:
- Prefer explicit user-provided context.
- If user text contains a ticket id pattern like
[A-Z]+-[0-9]+, use it as primary context (example:show me SCRUM-10). - Otherwise, infer the spec currently being worked on.
- Determine modality:
frontendwhen the spec includes UI behavior.backend-onlywhen it only defines API behavior.mixedwhen both exist.
- List concrete scenarios to demo from the spec acceptance criteria.
Step 1.1 - Anti-report guardrail
Before continuing, enforce this rule:
- Never finish after only analyzing requirements.
- Never return only a quick report when the user asked to "show" or "demo".
- If execution is blocked, explicitly report the blocker and ask for exactly what is needed to continue the live demo.
Step 2 - Frontend demonstration path
Run this path when modality is frontend or mixed.
- Start required local services if needed.
- Use browser automation to open the app and navigate to the target feature.
- Demonstrate feature behavior from the spec, one interaction at a time.
- Example sequence for list/table features:
- Open listing page
- Verify table data appears
- Use search box
- Apply filters
- Change sorting
- Open details view
- Example sequence for list/table features:
- After each meaningful action:
- Verify visible result matches spec expectations.
- Stop on a stable end state and let the user continue manual exploration or close the window.
- Keep the browser open unless the user asks to close it.
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.
- 11d ago First seen · 138 lines · 43 tokens per session scan A e78b1863ce36
show-spec-working is a skill published in the GitHub repository LIDR-academy/lidr-specboot (63 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 995 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…