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 enrich-usgit 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/enrich-us)<a href="https://agentmods.dev/skills/lidr-academy/lidr-specboot/enrich-us"><img src="https://agentmods.dev/badge/skills/lidr-academy/lidr-specboot/enrich-us/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/enrich-us"><img src="https://agentmods.dev/badge/skills/lidr-academy/lidr-specboot/enrich-us.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00464 |
| Opus 5.5 | $0.00009 | $0.00186 |
| Sonnet 5.5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
enrich-us 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 1mo 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
enrich-us Skill
Use it when this workflow is required in the project.
Instructions
Please analyze and enrich the ticket: $ARGUMENTS.
Follow these steps:
- Determine the ticket input source:
- Direct input mode (default when ticket text is provided): Use the ticket content shared by the user in the prompt/chat.
- Jira mode (optional): If the user provides a Jira id/key, or asks to use Jira (including references like "the one in progress"), use Jira MCP to fetch the ticket details.
- Act as a product expert with technical knowledge.
- Understand the problem described in the ticket.
- Decide whether or not the User Story is completely detailed according to product best practices. Validate that it includes:
- Full functionality description
- Comprehensive list of fields to update
- Required endpoints structure and URLs
- Files/modules to modify according to architecture and best practices
- Definition of done (implementation and delivery steps)
- Documentation and unit test updates
- Non-functional requirements (security, performance, observability, etc.)
- If the story lacks enough technical detail for autonomous implementation, provide an improved version that is clearer, more specific, and concise, aligned with step 4. Use project technical context from
@documentation. Return the result in markdown. - Output format must always include:
## Original## Enhanced
- Jira write-back is optional and only applies in Jira mode:
- Update the Jira ticket by appending the enhanced content after the original content, with clear
h2sections[original]and[enhanced]and readable formatting (lists/code snippets when useful). - If ticket status is
To refine, move it toPending refinement validation.
- Update the Jira ticket by appending the enhanced content after the original content, with clear
Notes
- Do not require Jira when the user already provided full ticket content directly.
- If input is ambiguous (for example, user gives a short reference without content), ask whether to resolve via Jira or request the full ticket text.
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.
- 1mo ago First seen · 42 lines · 23 tokens per session scan A d5d4edda3758
enrich-us is a skill published in the GitHub repository LIDR-academy/lidr-specboot (90 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 464 once invoked, about $0.0001 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.