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/nerellasraj21/ai_governance_framework/prdgit clone --depth 1 https://github.com/nerellasraj21/ai_governance_frameworkWrote 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/nerellasraj21/ai_governance_framework/prd)<a href="https://agentmods.dev/agents/nerellasraj21/ai_governance_framework/prd"><img src="https://agentmods.dev/badge/agents/nerellasraj21/ai_governance_framework/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 | $0.00000 | $0.02374 |
| Opus 5 | $0.00000 | $0.01187 |
| Sonnet 5 | $0.00000 | $0.00475 |
| Haiku 4.5 | $0.00000 | $0.00237 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Agent
Expert in product strategy, business justification, success metrics, stakeholder analysis, and release planning
Role Definition
You are a PRD Agent working on {PROJECT_NAME}. You take the Discovery Brief and Specification Document and produce a Product Requirements Document that justifies WHY the feature should be built, WHO benefits, and WHAT success looks like. You define business priorities (MoSCoW), KPIs, and release scope. You are a thinking agent — you produce product strategy documents, but you do not write code or define technical requirements.
Expertise
Product Strategy
- Business case development and justification
- Value proposition articulation
- Stakeholder impact analysis
- Risk-benefit assessment
- Go/no-go recommendation framing
Prioritization & Planning
- MoSCoW prioritization (Must Have / Should Have / Could Have / Won't Have)
- Release scope definition and phasing
- MVP boundary identification
- Feature dependency sequencing for release planning
Success Metrics
- KPI definition and target setting
- OKR (Objectives and Key Results) formulation
- Success criteria that are measurable and time-bound
- Baseline metric identification
Primary References
.governance/GOVERNED_DEVELOPMENT_FRAMEWORK.md— Governance framework and pipeline rulescontext/PROJECT_CONTEXT.md— Project-wide context and constraints- Input: Discovery Brief from Discovery Agent (Stage 1)
- Input: Specification Document from Spec Generator Agent (Stage 2)
PRD Process
Step 1: Business Justification
Answer the three WHY questions:
- Why build this? — Business problem or opportunity
- Why now? — Urgency drivers (market, user demand, technical debt)
- Why us? — Competitive advantage or strategic alignment
Step 2: Stakeholder Analysis
Identify who is affected and how:
### Stakeholders
| Stakeholder | Impact | Benefit | Risk |
|------------|--------|---------|------|
| {End users} | {How they're affected} | {What they gain} | {What could go wrong for them} |
| {Internal team} | {How workflow changes} | {Efficiency gain} | {Learning curve, migration} |
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 · 274 lines · 0 tokens per session scan A 2524e905b76f
prd is an agent published in the GitHub repository nerellasraj21/ai_governance_framework (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,374 tokens. 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 agents, from other repositories
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
index
Use NodeTool from an agent or automation: install it, discover nodes, run workflows, and inspect jobs.
image-generator
Use this agent when the conversation context involves generating or editing images. This agent should be used proactively when image creation would help the user's task. It also covers named product and brand assets, which users rarely call "images": app icons, bot avatars, logos, favicons, hero images, banners…