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 hamzaPixl/pixl-ai --skill prd-analysisgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/prd-analysis)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/prd-analysis"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/prd-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/prd-analysis"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/prd-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.02173 |
| Opus 5.5 | $0.00028 | $0.00869 |
| Sonnet 5.5 | $0.00014 | $0.00435 |
| Haiku 4.5 | $0.00007 | $0.00217 |
Grade A, and why
prd-analysis 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 1mo 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill sits at the top of the planning funnel — it takes a raw PRD or source document and produces a structured project foundation that downstream skills consume directly.
Raw PRD/source → /prd-analysis → structured .context/ → /task-plan, /sprint-planning, /prd-pipeline
Why this exists: /prd-pipeline goes end-to-end (PRD → code → PR) and /spec-review only works when code already exists. This skill fills the gap: "I have a raw PRD → produce a structured project overview → persist as artifacts → make available for downstream workflows."
Required References
Read these before starting:
references/analysis-categories.md— templates for the 8 analysis categoriesreferences/output-schema.md— JSON schema for requirements.json and project-overview.md structure../spec-review/references/requirement-decomposition.md— atomic requirement decomposition methodology (reuse, don't duplicate)
Step 1: Input Acquisition
Detect the input type and acquire the raw PRD content:
| Input Type | Detection | Action |
|---|---|---|
| File path | Contains /, .md, .txt, .pdf |
Read with Read tool |
| URL | Starts with http:// or https:// |
Fetch with WebFetch |
| Pasted text | Neither of the above | Use the argument text directly |
| No argument | Empty | Ask user via AskUserQuestion: "Please provide a PRD file path, URL, or paste the requirements text." |
After acquiring content:
- Create
.context/and.context/spec/directories if they don't exist:mkdir -p .context/spec - Save the raw PRD to
.context/prd.md(canonical location used by downstream skills) - Confirm to the user: source type, approximate length, and that it's saved to
.context/prd.md
Step 2: Structural Analysis
Parse the PRD into the 8 categories defined in references/analysis-categories.md:
- Project Overview — elevator pitch, goals, success metrics, target users
- Domain Model — entities, relationships, bounded contexts
- Architecture Overview — components, integrations, tech stack, deployment
- Milestones — phased delivery with objectives per phase
- Feature Breakdown — epics → features, MoSCoW priorities
- Technical Requirements — performance, security, scalability, accessibility
- Risks & Assumptions — probability, impact, mitigation strategies
- Open Questions — blocking vs informational, grouped by category
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 240 lines · 70 tokens per session scan A da7ca1762c51
prd-analysis is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 70 tokens to every session and 2,173 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.