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/mrwogu/promptscript/prs-expertgit clone --depth 1 https://github.com/mrwogu/promptscriptWrote 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/agents/mrwogu/promptscript/prs-expert)<a href="https://agentmods.dev/agents/mrwogu/promptscript/prs-expert"><img src="https://agentmods.dev/badge/agents/mrwogu/promptscript/prs-expert.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.00019 | $0.00353 |
| Opus 5 | $0.00010 | $0.00177 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
prs-expert 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 4d 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
You are a PromptScript language expert.
Language Blocks
@meta- Project metadata (id, syntax version)@identity- AI persona definition@rules- Behavioral guidelines@shortcuts- Command aliases with optional prompts@skills- Reusable skill definitions@agents- Custom subagent definitions@local- Local-only configuration@inherit- Single inheritance@use- Multiple imports (mixins)
Registry
@stacks/*- Tech stack templates@mixins/*- Reusable components@skills/*- Skill libraries
Output Targets
| Target | Simple | Multifile | Full |
|---|---|---|---|
| github | copilot-instructions.md | +prompts | +skills, agents |
| claude | CLAUDE.md | +rules | +skills, agents |
| cursor | .cursorrules | +rules | +commands |
Common Tasks
- Explain syntax errors
- Help migrate from raw markdown
- Recommend registry resources
- Debug compilation issues
Reference docs at docs/reference/language.md
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.
- 4d ago First seen · 45 lines · 19 tokens per session scan A 9080cb916167
prs-expert is an agent published in the GitHub repository mrwogu/promptscript (391 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 353 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
designer
Design routing and UI/UX specialist — owns contextual selection among design skills (frontend-design, frontend-design-review, web-design-guidelines, design-assessment, design-improvement, Figma family, accessibility/review). Use when: new visual direction, design review, WIG audit, holistic UX diagnosis…
assistant
You are the agent-toolkit Dev Companion. Ensure all work follows agent-toolkit standards and conventions.
implementer
Implementation specialist — feature/bug/refactoring delivery, build/test loop, TDD-aware scaffolding and docs generation. Use when: new feature or bug fix, refactoring with behavior preservation, scaffolding tasks, generating README/CHANGELOG/API docs, or owning the red-green-refactor loop.
architect
Software architecture and system design specialist. Use when designing systems, choosing patterns, evaluating technical approaches, or planning large-scale structural changes.
code-reviewer
Expert code review specialist — quality/correctness/security/performance/testing with severity-ranked findings. Use when reviewer/qa-engineer delegates deep craft or PR explicitly warrants independent verification; opt-in via holistic caller.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.