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/stchiotis/library-first-engineering/lfe-to-issuesnpx skills add StChiotis/Library-First-Engineering --skill lfe-to-issuesgit clone --depth 1 https://github.com/StChiotis/Library-First-EngineeringWrote 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/stchiotis/library-first-engineering/lfe-to-issues)<a href="https://agentmods.dev/skills/stchiotis/library-first-engineering/lfe-to-issues"><img src="https://agentmods.dev/badge/skills/stchiotis/library-first-engineering/lfe-to-issues.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 | $0.00037 | $0.00758 |
| Opus 5 | $0.00018 | $0.00379 |
| Sonnet 5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
lfe-to-issues 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFE To Issues
Position in Pipeline
- Phase: 1 (Architect sub-pipeline, Step 3)
- Persona: Architect
- Input:
.plans/02_prd.md - Output:
.plans/03_slices.md - Gate: 🛑 Human must approve slices before proceeding
Process
1. Read input
Read .plans/02_prd.md as the source of truth — it carries this step's inputs, not the conversation.
2. Draft vertical slices
Break the PRD into tracer bullet slices. Each slice is a thin vertical cut through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
Slices are either:
- AFK — can be implemented and merged without human interaction
- HITL — requires a human decision, design review, or external dependency
Prefer AFK over HITL where possible.
Vertical slice rules:
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
- A completed slice is demoable or verifiable on its own
- Prefer many thin slices over few thick ones
3. Present to human
Present the proposed breakdown as a numbered list. For each slice show:
- Title: short descriptive name
- Type: HITL / AFK
- Blocked by: which other slices must complete first
- User stories covered: which user stories this addresses
Ask the human:
- Does the granularity feel right?
- Are the dependency relationships correct?
- Should any slices be merged or split further?
- Are the correct slices marked as HITL and AFK?
🛑 Iterate until the human approves the breakdown.
4. Write coordination file
Save approved slices to .plans/03_slices.md:
---
phase: architect
step: 3_slices
status: complete
timestamp: <ISO-8601>
source: .plans/02_prd.md
total_slices: <N>
approved_by_human: true
---
## Slice 1: <Title>
- **Type**: AFK
- **Blocked by**: None
- **Acceptance criteria**:
- [ ] Criterion 1
- [ ] Criterion 2
## Slice 2: <Title>
- **Type**: AFK
- **Blocked by**: Slice 1
- **Acceptance criteria**:
- [ ] Criterion 1
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 · 84 lines · 37 tokens per session scan A 12d109020aa7
lfe-to-issues is a skill published in the GitHub repository StChiotis/Library-First-Engineering (43 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 758 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.
Other skills, from other repositories
playwright
Use when the task requires capturing or automating a real browser from the terminal.
implementation-final-review
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…
promptfoo-provider-setup
Configure promptfoo providers or redteam targets for hosted models, live HTTP APIs, Python/JavaScript local scripts, agent SDKs, or multi-input systems. Use when connecting promptfoo to the system under test, mapping vars, auth env vars, request bodies, response transforms, or static-code-derived provider wrappers. Do…
redteam-plugin-development
Standards for creating redteam plugins and graders. Use when creating new plugins, writing graders, or modifying attack templates.
search-params
URL search param and hash state management. Use when adding or modifying URL search params, working with useSearchParams, setSearchParams, useSearchParamState, or navigate() with query strings or hash fragments, or fixing browser back/forward button issues.
prior-auth-packet-builder
Build a concise prior authorization packet from local case files and payer policy docs.