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/contextgit 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/context)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/context"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/context.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.00014 | $0.02656 |
| Opus 5 | $0.00007 | $0.01328 |
| Sonnet 5 | $0.00003 | $0.00531 |
| Haiku 4.5 | $0.00001 | $0.00266 |
Grade A, and why
context 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Command
Display your current development context to quickly resume work after interruptions.
Purpose
Answer the question: "Where am I and what was I doing?"
Essential for:
- 🔄 Resuming work after meetings/interruptions
- 🎯 Remembering which PRD you're on
- 📊 Seeing progress at a glance
- ⚡ Quick status check without digging through files
Usage
# Show current context
/context
# Show context for specific worktree
/context --worktree=worktrees/prd-007/
# Verbose mode (includes recent commits, todos)
/context --verbose
/context -v
Workflow
Step 1: Detect Current Location
# Get current Git branch
CURRENT_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
# Detect if in worktree
if git rev-parse --git-common-dir &>/dev/null; then
GIT_COMMON_DIR=$(git rev-parse --git-common-dir)
if [[ "$GIT_COMMON_DIR" != *".git"* ]] || [[ "$GIT_COMMON_DIR" == *"worktrees"* ]]; then
IN_WORKTREE=true
WORKTREE_PATH=$(pwd)
else
IN_WORKTREE=false
WORKTREE_PATH=""
fi
else
IN_WORKTREE=false
WORKTREE_PATH=""
fi
Step 2: Extract PRD Information
From branch name:
# Extract PRD ID from branch name (supports various formats)
# Examples: feat/PRD-007-oauth, feature/WTC-PRD-007-oauth, PRD-007-oauth
if [[ "$CURRENT_BRANCH" =~ (PRD-[0-9]+) ]]; then
PRD_ID="${BASH_REMATCH[1]}"
elif [[ "$CURRENT_BRANCH" =~ ([A-Z]+-PRD-[0-9]+) ]]; then
PRD_ID="${BASH_REMATCH[1]}"
else
PRD_ID="unknown"
fi
Find PRD file:
# Search for PRD file across directories
PRD_FILE=$(find product/prds/ -name "*${PRD_ID}*.md" 2>/dev/null | head -n 1)
if [ -n "$PRD_FILE" ]; then
# Extract metadata from PRD
PRD_TITLE=$(grep -m1 '^#' "$PRD_FILE" | sed 's/^#\+\s*//' | sed "s/${PRD_ID}:\s*//")
PRD_STATUS=$(grep -m1 '^\*\*Status\*\*:' "$PRD_FILE" | sed 's/^\*\*Status\*\*:\s*//' || echo "Unknown")
PRD_PRIORITY=$(grep -m1 '^\*\*Priority\*\*:' "$PRD_FILE" | sed 's/^\*\*Priority\*\*:\s*//' || echo "-")
PRD_ASSIGNEE=$(grep -m1 '^\*\*Assignee\*\*:' "$PRD_FILE" | sed 's/^\*\*Assignee\*\*:\s*//' || echo "-")
# Determine directory/stage
if [[ "$PRD_FILE" == *"01-draft"* ]]; then
PRD_STAGE="Draft"
elif [[ "$PRD_FILE" == *"02-ready"* ]]; then
PRD_STAGE="Ready"
elif [[ "$PRD_FILE" == *"03-in-progress"* ]]; then
PRD_STAGE="In Progress"
elif [[ "$PRD_FILE" == *"04-complete"* ]]; then
PRD_STAGE="Complete"
else
PRD_STAGE="Unknown"
fi
fi
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 · 372 lines · 14 tokens per session scan A 1a2ef68e14cc
context is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 14 tokens to every session and 2,656 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
brooks-debt
Run a Brooks-Lint tech debt assessment.
brooks-health
Run a Brooks-Lint codebase health dashboard across all four dimensions.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
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.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.