A document lookup tool that finds Product Requirements Documents, Feature Requirements Documents, technical specifications, and RFCs by ID, name, or file path. It loads the matching document into the agent’s working context.

Use it to bring product plans, feature requirements, technical specifications, or design proposals into a coding session.

It removes the need to manually search for and open project documents before asking the agent to use them.

ctx — Skill for Claude Code by jpoutrin/product-forge

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/jpoutrin/product-forge

agentmods

npx agentmods add skills/jpoutrin/product-forge/ctx

Made for: Claude Code.

Or install product-design, the plugin that ships this one along with the rest of its 43 skills, 8 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/ctx/github.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/ctx)

Your own site

<a href="https://agentmods.dev/skills/jpoutrin/product-forge/ctx"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/ctx/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jpoutrin/product-forge/ctx"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/ctx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,534 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.01534
Opus 5.5	$0.00006	$0.00614
Sonnet 5.5	$0.00003	$0.00307
Haiku 4.5	$0.00002	$0.00153

Measured 1mo ago against content hash 703f6dcadd6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ctx 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.

plugins/product-design/skills/ctx/SKILL.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ctx (Context Hydration)

Category: Context Management

Usage

/ctx <doc-reference>

Arguments

<doc-reference>: Required - Document identifier or path. Accepts:
- Document IDs: PRD-001, FRD-042, TS-0045, RFC-0042
- Partial names: user-auth, payment-gateway
- File paths: ./product-docs/prds/active/user-auth-prd.md

Execution Instructions for Claude Code

When this command is run, Claude Code should:

Identify Document Type and Location

Search order by ID prefix:

Prefix Type Search Locations

PRD- Product PRD product-docs/prds/

FRD- Feature PRD product-docs/prds/

TS- Tech Spec tech-specs/

RFC- RFC rfcs/

If no prefix, search all locations for partial name match.

Prefix	Type	Search Locations
`PRD-`	Product PRD	`product-docs/prds/`
`FRD-`	Feature PRD	`product-docs/prds/`
`TS-`	Tech Spec	`tech-specs/`
`RFC-`	RFC	`rfcs/`

Search for Document

# Search patterns by type
PRD/FRD: product-docs/prds/**/*<query>*.md
Tech Spec: tech-specs/**/*<query>*.md
RFC: rfcs/**/*<query>*.md

Handle Multiple Matches

If multiple documents match, display options:

Multiple documents match "auth":

1. PRD-001-user-authentication-prd.md (PRD)
2. FRD-015-oauth-integration-frd.md (FRD)
3. TS-0044-auth-implementation.md (Tech Spec)
4. RFC-0043-auth-redesign.md (RFC)

Which document to load? [1-4]

Read and Present Document

Read the full document content and present with context header:

═══════════════════════════════════════════════════════════
📄 CONTEXT LOADED: PRD-001 - User Authentication System
═══════════════════════════════════════════════════════════

Type:     Product PRD
Status:   ACTIVE
Version:  1.2
Location: product-docs/prds/active/PRD-001-user-authentication-prd.md

Related Documents:
- Tech Spec: TS-0044-auth-implementation.md
- Tasks: tasks/PRD-001-tasks.md

───────────────────────────────────────────────────────────

[Full document content here]

═══════════════════════════════════════════════════════════
Context loaded. Ready to work on this document.
═══════════════════════════════════════════════════════════

Read the full file on GitHub · 229 lines

Changes

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 · 229 lines · 16 tokens per session scan A 703f6dcadd6a

Subscribe to this mod's changes

ctx is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 1,534 once invoked, about $0.0001 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.

Documents Memory and context

cua-volume

Use Cua Volume, the one volume every Space and agent of this user shares. Inside a Space it is mounted as a folder (/volume on Linux, /Cua Volume on macOS), so any program reads and writes it directly. Use it for anything that must outlive this Space - your memory and outputs in your agent home, shared reference in…

trycua/cua · 114 tokens

obsidian

Obsidian vault: search/read/write notes, backlinks, Bases, Canvas.

steipete/agent-scripts · 19 tokens

loopx-doc-registry

Use when a connected LoopX project is asked to read, remember, record, index, register, or use a durable project material such as a Lark/wiki/design doc, research note, SOP, owner packet, migration report, benchmark paper, or external material source. Use even when the user does not mention LoopX or doc registry.

huangruiteng/loopx · 74 tokens

ctx