list-tech-specs

list-tech-specs is a skill for Claude Code from jpoutrin/product-forge. It costs 0 tokens per session (878 once invoked), scanned A, original, MIT.

A command for finding technical specifications in a project's tech-specs folders and showing their status and metadata. Technical specifications are documents that describe how a system or feature should be built.

In plain words
What is it for?
Use it to list specification IDs, titles, authors, dates, statuses, and related RFCs, with an option to include archived documents.
Why use it?
It avoids opening files one by one to find which specifications are drafts, approved, references, or archived. Results can be narrowed by status or linked RFC.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

Part of the devops-data plugin — 17 skills, 4 agents shipped together

Install

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.

agentmods
npx agentmods add skills/jpoutrin/product-forge/list-tech-specs
Any agent
npx skills add jpoutrin/product-forge --skill list-tech-specs
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install devops-data, the plugin that ships this one along with the rest of its 17 skills, 4 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.

agentmods badge for list-tech-specs

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/list-tech-specs.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/list-tech-specs)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/list-tech-specs"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/list-tech-specs.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 878 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00878
Opus 5 $0.00000 $0.00439
Sonnet 5 $0.00000 $0.00176
Haiku 4.5 $0.00000 $0.00088

Measured 6d ago against content hash 2d2b6629111b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

list-tech-specs 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.

plugins/devops-data/skills/list-tech-specs/SKILL.md · 148 lines

How it starts

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

list-tech-specs

Category: Technical Architecture

Usage

/list-tech-specs [options]

Options

Option Description
--status <status> Filter by status (DRAFT, APPROVED, REFERENCE)
--all Include archived specs
--rfc <RFC-XXXX> Filter by linked RFC
`--format table list`

Execution Instructions

When this command is run, Claude Code should:

  1. Scan Tech Spec Directories

    tech-specs/
    ├── draft/      → DRAFT
    ├── approved/   → APPROVED
    ├── reference/  → REFERENCE
    └── archive/    → (only with --all)
    
  2. Extract Metadata from Each Spec

    • Tech Spec ID (from filename or frontmatter)
    • Title
    • Status
    • Author
    • Linked RFC (if any)
    • Created date
    • Last updated date
  3. Apply Filters (if specified)

    • Filter by status
    • Filter by linked RFC
    • Exclude archive unless --all
  4. Display Results

Table Format (default)

Tech Spec Summary
=================

Active: 8 | Reference: 15 | Archived: 5

| Spec ID   | Title                      | Status    | RFC Link  | Updated    |
|-----------|----------------------------|-----------|-----------|------------|
| TS-0045   | Payment Gateway API        | APPROVED  | RFC-0042  | 2025-12-05 |
| TS-0044   | User Auth Implementation   | DRAFT     | -         | 2025-12-04 |
| TS-0043   | Cache Layer Design         | REFERENCE | RFC-0038  | 2025-12-01 |
| TS-0042   | Search Service             | APPROVED  | -         | 2025-11-28 |

Use '/tech-spec-status TS-XXXX' to see details or update status.

List Format

TS-0045: Payment Gateway API
  Status: APPROVED
  Author: Jane Doe
  RFC: RFC-0042
  Created: 2025-12-01
  Updated: 2025-12-05
  Location: tech-specs/approved/TS-0045-payment-gateway-api.md

TS-0044: User Auth Implementation
  Status: DRAFT
  Author: John Doe
  RFC: -
  ...

Status Summary

Always show a summary at the top:

Read the full file on GitHub · 148 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.

  1. 6d ago First seen · 148 lines · 0 tokens per session scan A 2d2b6629111b

Subscribe to this mod's changes

list-tech-specs is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 878 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-30.

Related

Other skills, from other repositories

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

baoyu-youtube-transcript

Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…

JimLiu/baoyu-skills · 107 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

gog-slides

Google Slides operations through gog.

openclaw/gogcli · 11 tokens

read

Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…

tw93/Waza · 78 tokens