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/jsuvic/agent-profile/request-to-spec-issuesnpx skills add jsuvic/agent-profile --skill request-to-spec-issuesgit clone --depth 1 https://github.com/jsuvic/agent-profileWrote 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/jsuvic/agent-profile/request-to-spec-issues)<a href="https://agentmods.dev/skills/jsuvic/agent-profile/request-to-spec-issues"><img src="https://agentmods.dev/badge/skills/jsuvic/agent-profile/request-to-spec-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.1 | $0.00033 | $0.01334 |
| Opus 5 | $0.00016 | $0.00667 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
request-to-spec-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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Request To Spec Issues
Purpose
Convert a completed grill-change agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs. Preserve product intent and decision rules so implementation choices follow the agreed direction.
Preconditions
- The grill is complete and its agreement record is approved.
- That grill approval authorizes this synthesis and one bounded local persistence step; do not ask for a second product-level approval.
- Relevant local specs, ADRs, docs, fixtures, and code context have been checked.
- If there is no completed grill agreement, stop and run
grill-changefirst.
Synthesis Rules
- Do not re-interview the user except on a derivation exception - a contradiction, a missing material decision, or scope expansion (see Derivation Exceptions).
- Keep product intent, non-goals, durable terms, and hard-to-reverse decisions above implementation mechanics.
- Preserve existing spec contracts and safety rules unless the user explicitly approved changing them.
- Split work into vertical behavior slices, not file layers.
- Make every issue small enough for a focused RED, GREEN, refactor loop.
- Mark dependencies and parallel-safe work explicitly.
- Propose architecture rescue candidates before feature slices when a change would deepen an already fragmented codebase.
Architecture Rescue Candidates
When architecture rescue is needed, propose candidates before feature issues. Each candidate must include:
- Files or modules involved
- Current friction
- Proposed deeper module or clearer interface
- Expected locality and leverage improvement
- Expected test improvement
- ADR or spec conflicts
- Recommended dependency state: prerequisite, parallel, or later cleanup
Spec Candidate
Include these sections:
- Status
- Problem
- Goal
- Intent
- Decision Rules
- Non-Goals
- User Flow
- Inputs
- Outputs
- Contracts
- Security Rules
- Acceptance Criteria
- Tests
- TDD Strategy
- Issue Plan
- Documentation Updates
- Final Review Checklist
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 · 160 lines · 33 tokens per session scan A 6d5e741a4e66
request-to-spec-issues is a skill published in the GitHub repository jsuvic/agent-profile (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,334 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-31.
Other skills, from other repositories
recursive-implement
Build a project using recursive multi-agent development with TDD.
recursive-development
Core principles for recursive multi-agent development -- nesting, scope ownership, TDD, context flow, token economics.
cm-tdd
Use when implementing any feature or bugfix, before writing implementation code.
tdd-loop
Implement a known feature, behavior change, or diagnosed bug with a red-green-refactor loop. Use when the user asks to add, build, implement, or fix behavior and automated tests exist or should exist. For an unknown failure cause use debug-protocol first; for model, prompt, RAG, or agent quality use…
python-testing
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
tastemaker
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble…