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 skills/p47phoenix/claude-plugins/descriptivenpx skills add P47Phoenix/Claude-Plugins --skill descriptivegit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/p47phoenix/claude-plugins/descriptive)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/descriptive"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/descriptive.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.00061 | $0.00980 |
| Opus 5 | $0.00030 | $0.00490 |
| Sonnet 5 | $0.00012 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
research-types-descriptive 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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Descriptive Research Sub-Skill
Router-dispatched paradigm sub-skill for Descriptive research. Not directly model-invocable; the research-agent parent loads this sub-skill only when Phase 1 detection classifies the question as Descriptive.
When This Sub-Skill Loads
The parent router dispatches here when the input question contains signals like:
- "What is the current state of X"
- "What exists in the X landscape"
- "Map / Document / Inventory / Survey / Catalogue"
- "List the available X"
- Field-survey or technology-landscape requests where the goal is to describe what exists
Disambiguation rule (from research-agent/references/research-type-patterns.md):
"What is the current adoption of X" (mapping a fact) → Descriptive. "Was X adoption successful" (judging merit) → Evaluative.
Framework Selection
| Framework | Use When |
|---|---|
| SPICE | Context-specific landscape ("what is the state of testing tools in mobile-first teams") |
| None | Open-domain inventory or survey; no perspective filter needed |
PICO/PECO are not used for Descriptive work — there is no intervention or exposure being evaluated; the goal is enumeration.
Output Pattern: Landscape Map
Use this pattern verbatim for the Findings section (parent skill's Phase 6 Synthesis output):
## Research Type: Descriptive
## Framework: [None / SPICE]
## Domain Boundaries
[Clear definition of what is and is not in scope]
## Entity Inventory
| Entity | Type | Key Properties | Source |
|--------|------|----------------|--------|
| ... | ... | ... | [S1] |
## Relationship Map
[Describe connections between entities - who uses what, what depends on what]
## State of the Field (as of [date])
- Mature / established: [...]
- Emerging: [...]
- Deprecated / declining: [...]
## Gaps in Documentation
[What exists but is undocumented, or documented inconsistently]
Phase Adaptations
The parent skill's 8-phase flow applies. Descriptive-specific notes:
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.
- 3d ago First seen · 88 lines · 61 tokens per session scan A a585c7b53e9b
research-types-descriptive is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 980 once invoked, about $0.0003 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-31.
Other skills, from other repositories
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…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
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…
docx-comment-reply
Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.