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 commands/yassinello/claude-plugin-prd-workflow/recallgit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/commands/yassinello/claude-plugin-prd-workflow/recall)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/recall"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/recall.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.1 | $0.00015 | $0.02716 |
| Opus 5 | $0.00008 | $0.01358 |
| Sonnet 5 | $0.00003 | $0.00543 |
| Haiku 4.5 | $0.00002 | $0.00272 |
Grade A, and why
recall 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 6d 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recall Command
Search project history for past PRDs, decisions, and learnings.
Purpose
Enable quick access to historical context:
- Find similar past features ("How did we implement OAuth?")
- Recall technical decisions ("What database schema did we use?")
- Learn from past blockers ("What issues came up with Stripe integration?")
- Discover reusable patterns ("Show me all API implementations")
Usage
Basic Search (Full-Text)
/recall "OAuth implementation"
/recall "Stripe payment"
/recall "database schema"
Filters
# Search only completed PRDs
/recall "authentication" --status=complete
# Search by priority
/recall "feature" --priority=P0
# Search by date range
/recall "api" --since=30d
/recall "bug" --before=2025-10-01
# Search specific PRD
/recall "performance" --prd=PRD-003
Semantic Search (Optional)
# Find similar features (requires embeddings)
/recall --similar-to=PRD-003
/recall --similar-to="real-time chat"
Workflow
Step 1: Initialize Memory Index (First Run)
On first use, create SQLite FTS5 index:
→ Initializing search index...
→ Scanning product/prds/...
• Found 25 PRDs
• Indexing content...
• Building FTS5 index...
✓ Index created (.claude/memory/index.db)
This will speed up future searches significantly.
Index updates automatically when PRDs change.
Step 2: Full-Text Search
Search using SQLite FTS5:
SELECT
prd_id,
name,
status,
priority,
snippet(prds_fts, -1, '<mark>', '</mark>', '...', 30) AS snippet,
rank
FROM prds_fts
WHERE prds_fts MATCH 'oauth OR authentication'
ORDER BY rank
LIMIT 10;
Step 3: Rank and Display Results
Show most relevant PRDs:
🔍 Search Results for "OAuth implementation"
Found 3 matches:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 PRD-003: User Authentication System
✅ Status: Complete | P0 | Completed 2 months ago
🔑 Key Decisions:
• Used OAuth 2.0 with PKCE flow
• Chose NextAuth.js over Passport.js
• Token refresh every 30 minutes
• Stored refresh tokens in HttpOnly cookies
⚠️ Blockers Encountered:
• CORS issues with Google OAuth (fixed with proxy)
• Token rotation edge cases (solved in v1.1)
• Safari third-party cookie restrictions (used workaround)
💡 Learnings:
• Always test token expiration scenarios
• Document OAuth redirect URLs clearly
• Consider token security vs UX tradeoffs
📎 Related PRDs:
• PRD-007: SSO Integration (similar pattern)
• PRD-012: API Authentication (depends on this)
📄 File: product/prds/04-complete/241015-user-auth-PRD-003-v1.md
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 PRD-007: SSO Integration
🚧 Status: In Progress | P1 | Day 3
Snippet: "...building on <mark>OAuth</mark> foundation from PRD-003, add SAML..."
📄 File: product/prds/03-in-progress/241020-sso-PRD-007-v1.md
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 PRD-012: Third-Party API Auth
✅ Status: Ready | P0
Snippet: "...reuse <mark>OAuth</mark> client credentials flow for API-to-API..."
📄 File: product/prds/02-ready/241023-api-auth-PRD-012-v1.md
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
💡 Quick Actions:
• View PRD-003: Read PRD-003 file
• Copy decision: "Used OAuth 2.0 with PKCE flow"
• Find more: /recall "authentication" --status=complete
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.
- 6d ago First seen · 449 lines · 15 tokens per session scan A 226e08ebbcb8
recall is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 2,716 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 commands, from other repositories
mem-search
Search past observations and context from claude-mem persistent memory.
pause
Save session context for handoff to a future session.
resume
Restore context from a previous session and continue work.
learn
Force claude-smart to extract learnings from this session now.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
init
Install the formatters this repository needs, with every command visible before it runs.