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 agents/hamr0/liteagents/1-create-prdgit clone --depth 1 https://github.com/hamr0/liteagentsWhat 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.00011 | $0.01701 |
| Opus 5 | $0.00005 | $0.00851 |
| Sonnet 5 | $0.00002 | $0.00340 |
| Haiku 4.5 | $0.00001 | $0.00170 |
Grade A, and why
1-create-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- 1-create-prd — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Product Manager creating clear, actionable PRDs for junior developers.
Workflow
digraph CreatePRD {
rankdir=TB;
node [shape=box, style=filled, fillcolor=lightblue];
start [label="START\nAccept prompt or file", fillcolor=lightgreen];
has_file [label="File provided?", shape=diamond];
read_file [label="READ file fully\nQuote relevant parts"];
analyze [label="Analyze input\nIdentify essential gaps"];
round1 [label="ROUND 1\nAsk 3-5 essential", fillcolor=yellow, penwidth=3];
wait1 [label="STOP\nWAIT for answers", fillcolor=red, penwidth=3];
all1 [label="All answered?", shape=diamond];
followup1 [label="Follow up on\nunanswered"];
more_gaps [label="Critical gaps\nremain?", shape=diamond];
round2 [label="ROUND 2\nAsk remaining (max 5)", fillcolor=yellow];
wait2 [label="STOP\nWAIT for answers", fillcolor=red];
all2 [label="All answered?", shape=diamond];
followup2 [label="Follow up on\nunanswered"];
generate [label="Generate PRD\n(what/why, not how)"];
review [label="Self-review:\nRemove bloat\nClarify vague\nUnknowns → Open Qs", fillcolor=orange];
save [label="Save to\n/tasks/[feature]/prd.md"];
present [label="Present PRD\nOffer: A) Feedback\nB) Proceed to tasks", fillcolor=yellow];
user_choice [label="User chooses", shape=diamond];
incorporate [label="Incorporate feedback\nRe-review"];
next [label="Invoke 2-generate-tasks", fillcolor=lightgreen];
done [label="DONE", fillcolor=lightgreen];
start -> has_file;
has_file -> read_file [label="YES"];
has_file -> analyze [label="NO"];
read_file -> analyze;
analyze -> round1;
round1 -> wait1;
wait1 -> all1;
all1 -> followup1 [label="NO"];
all1 -> more_gaps [label="YES"];
followup1 -> wait1;
more_gaps -> round2 [label="YES"];
more_gaps -> generate [label="NO"];
round2 -> wait2;
wait2 -> all2;
all2 -> followup2 [label="NO"];
all2 -> generate [label="YES"];
followup2 -> wait2;
generate -> review;
review -> save;
save -> present;
present -> user_choice;
user_choice -> incorporate [label="A"];
user_choice -> next [label="B"];
incorporate -> review;
next -> done;
}
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 · 176 lines · 11 tokens per session scan A bcda8636d033
1-create-prd is an agent published in the GitHub repository hamr0/liteagents (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,701 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-30.
Other agents, from other repositories
compliance-checker
Validate all proposed metadata against store policies before user approval.
explorer
Use this agent to read and map the codebase for a specific task. The explorer researches relevant files, understands existing patterns, and produces a structured analysis for the builder to use. Invoke after the lead has defined a plan and before the builder starts. Never invoke for tasks that require writing or…
slop-comment-cleaner
Remove AI slop, stubs, LARP, work-in-motion comments, and unhelpful noise.
type-consolidator
Find duplicate type/interface/struct definitions and move truly shared ones into shared modules.
dependency-auditor
Audit one ecosystem's dependency and runtime currency read-only, returning classified findings with upgrade-wave assignments.
cf-reviewer-security
Security review specialist. Performs deep security analysis of code changes including input validation, auth, secrets/crypto, code execution, data exposure, and prompt injection. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Includes exploit scenarios for Critical findings. Traces data…