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 yugasun/aiops --skill to-prdgit clone --depth 1 https://github.com/yugasun/aiopsWrote 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/yugasun/aiops/to-prd)<a href="https://agentmods.dev/skills/yugasun/aiops/to-prd"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/to-prd.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.00029 | $0.00484 |
| Opus 5 | $0.00015 | $0.00242 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
to-prd 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 8d 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.
What it actually says
Synthesize context into a PRD. Do not interview — use the conversation and codebase.
Run /aiops-setup if docs/agents/issue-tracker.md or triage labels are missing.
Process
- Explore repo if needed. Use
CONTEXT.mdvocabulary and local ADRs. - Sketch test seams — prefer existing, highest seam, fewest seams. Confirm with user.
- Write PRD (template below) and publish to issue tracker with
ready-for-agentlabel.
PRD template
Problem Statement — user-facing problem.
Solution — user-facing solution.
User Stories — numbered As a <actor>, I want <feature>, so that <benefit> (extensive list).
Implementation Decisions — modules, interfaces, architecture, schema, API (no file paths; prototype snippets OK if they encode a decision).
Testing Decisions — what good tests look like, modules to test, prior art.
Out of Scope
Further Notes
Delta mode (brownfield changes)
When the PRD describes changes to an existing system (not a greenfield feature), use delta format instead of the full template above. Focus only on what changes:
# PRD: <slug> (delta)
## Context
One paragraph on what already exists and why it's changing.
## Changes
### ADDED
- New behavior or interface being introduced
- New modules, endpoints, or data structures
### MODIFIED
- [existing behavior] → [new behavior]
- [existing interface] → [updated interface]
### REMOVED
- Deprecated behavior being removed
- Modules or interfaces being deleted
## Impact
- Which existing modules are affected
- Migration path for breaking changes
## Testing
- What existing tests need updating
- New tests for added/modified behavior
## Out of Scope
When to use delta: if tech-spec.md references modifications to existing modules (not purely new code), prefer delta format. The conductor or planner should suggest delta when the architecture scan or design reveals significant existing code involvement.
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.
- 8d ago First seen · 69 lines · 29 tokens per session scan A 54af7b64a84b
to-prd is a skill published in the GitHub repository yugasun/aiops (4 stars, last pushed 19d ago), licensed Apache-2.0. It adds 29 tokens to every session and 484 once invoked, about $0.0001 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
hashiiiii-issues
Use this skill to create or edit GitHub issues with a consistent body structure.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
plan
Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
yida-agent-center
An agent-management tool for Yida, a business workflow platform. It manages temporary substitutes who handle or submit approval processes for current employees or departed employees.
yida-voc
A template for organising user feedback (VOC, or voice of the customer) about problems, requests, and performance issues in the Yida platform.
plan-to-issues
Convert any phased plan file, or a conversation about what to build, into labelled GitHub issues under one tracking epic mapping each issue to its source task. No plan file required. Don't use for writing plans, resolving issues, or triage.