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/makigjuro/cloudstack-ai-plugins/prdnpx skills add makigjuro/cloudstack-ai-plugins --skill prdgit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWhat 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.00034 | $0.02010 |
| Opus 5 | $0.00017 | $0.01005 |
| Sonnet 5 | $0.00007 | $0.00402 |
| Haiku 4.5 | $0.00003 | $0.00201 |
Grade A, and why
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 2d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator
Create a detailed, engineer-focused Product Requirements Document through structured discovery. The PRD is optimized for AI-assisted development and integrates with the /plan-feature workflow.
Configuration
Read cloudstack.json from the project root at the start of execution. Extract relevant fields:
SERVICES=backend.services[](default: discover from project structure)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
Arguments
{name}-- Short feature name for the file (optional, will prompt if not provided)--minimal-- Use minimal template for simple features--skip-analysis-- Skip codebase analysis (faster, for greenfield features)
Process
Phase 0: Enter Plan Mode
Always start by calling EnterPlanMode before doing anything else. PRD generation is a planning activity -- it requires codebase exploration, discovery questions, and user alignment before producing output. Plan mode ensures you can explore freely and get user sign-off on the approach before writing the PRD file. Exit plan mode with ExitPlanMode only after Phase 4 validation is complete and the user has approved the PRD content.
Phase 1: Discovery Questions
Ask the user these questions using AskUserQuestion. Group related questions together.
Problem & Users
- What problem are we solving? What's the business impact if we don't solve it?
- Who are the primary users?
- What's their current workaround, if any?
Success & Scope 4. How will we measure success? What metrics matter? 5. What's explicitly OUT of scope for this feature? 6. Are there related features we should be aware of but not implement now?
Technical Context
7. Which services will this touch? (list from SERVICES config or discovered services)
8. Are there external system integrations?
9. Any specific performance requirements? (latency, throughput, scale)
Constraints 10. Timeline or deadline constraints? 11. Backward compatibility requirements? 12. Security or compliance considerations?
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.
- 2d ago First seen · 309 lines · 34 tokens per session scan A d787a2b41c78
prd is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 2,010 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
omh-agent-board
This is a Hermes-native agent-board workflow skill.
omh-feedback-triage
This is a Hermes-native feedback-triage workflow skill.
triage-sweep
Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by…
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.
meeting-minutes
Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…