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 skills add prime-radiant-inc/greenfield --skill doc-researchgit clone --depth 1 https://github.com/prime-radiant-inc/greenfieldWrote 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/prime-radiant-inc/greenfield/doc-research)<a href="https://agentmods.dev/skills/prime-radiant-inc/greenfield/doc-research"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/doc-research/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.
<a href="https://agentmods.dev/skills/prime-radiant-inc/greenfield/doc-research"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/doc-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 197 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 243 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 271 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00039 | $0.04113 |
| Opus 5 | $0.00019 | $0.02056 |
| Sonnet 5 | $0.00008 | $0.00823 |
| Haiku 4.5 | $0.00004 | $0.00411 |
Grade A, and why
doc-research 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 11d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Research Methodology
This skill defines the complete methodology for extracting behavioral specifications from public documentation. Follow it step by step. Every section is normative.
1. Search Sequence
Search proceeds from most authoritative to least authoritative. Execute every pattern in each tier before moving to the next tier.
digraph search_sequence {
rankdir=TB;
"Start documentation research" [shape=doublecircle];
"Search Tier 1: Official documentation" [shape=box];
"Traverse full official site structure" [shape=box];
"Search Tier 2: Machine-readable specs" [shape=box];
"Search Tier 3: Community knowledge" [shape=box];
"Diminishing returns?" [shape=diamond];
"Page budget exhausted?" [shape=diamond];
"Write claims file and gaps file" [shape=box];
"Run gap analysis by product type" [shape=box];
"Research complete" [shape=doublecircle];
"Start documentation research" -> "Search Tier 1: Official documentation";
"Search Tier 1: Official documentation" -> "Traverse full official site structure";
"Traverse full official site structure" -> "Search Tier 2: Machine-readable specs";
"Search Tier 2: Machine-readable specs" -> "Search Tier 3: Community knowledge";
"Search Tier 3: Community knowledge" -> "Diminishing returns?";
"Diminishing returns?" -> "Write claims file and gaps file" [label="yes"];
"Diminishing returns?" -> "Page budget exhausted?" [label="no"];
"Page budget exhausted?" -> "Write claims file and gaps file" [label="yes"];
"Page budget exhausted?" -> "Search Tier 3: Community knowledge" [label="no, continue"];
"Write claims file and gaps file" -> "Run gap analysis by product type";
"Run gap analysis by product type" -> "Research complete";
}
Tier 1: Official Documentation (source type: official-docs)
Execute these search patterns in order. Replace {product} with the target product name and {domain} with the official domain if known.
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.
- 11d ago First seen · 417 lines · 39 tokens per session scan A 98425b2d3f8b
doc-research is a skill published in the GitHub repository prime-radiant-inc/greenfield (277 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 4,113 once invoked, about $0.0002 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 skills, from other repositories
benchmark
Local-only regression / benchmark skill for ui-clone-skills maintainers. Drives the standard ui-reverse-engineering pipeline against the canonical reference site (https://realfood.gov) and records AE/SSIM, iteration count, gate fail counts, and outcome to benchmark/history.csv so prompt / sub-doc / model-version drift…
write-test-plans
Interactive workflow for writing new Speky test plans for requirements lacking coverage, guided by the Speky MCP server.
speky-workflow
Guidelines for working with Speky requirements and tests via the speky MCP server tools.
SPI Flash Dump via OpenOCD
This skill should be used when the user asks to "dump SPI flash", "read EEPROM through OpenOCD", "dump flash via MCU", "read SPI through debug interface", "extract firmware from SPI", or mentions scenarios involving SPI flash connected to a microcontroller with SWD/JTAG debug access. Provides comprehensive guidance…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
review
5-pass structured code review — correctness, security, performance, readability, consistency.