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 srinidhis05/agentura --skill pr-doc-generatorgit clone --depth 1 https://github.com/srinidhis05/agenturaWrote 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/srinidhis05/agentura/pr-doc-generator)<a href="https://agentmods.dev/skills/srinidhis05/agentura/pr-doc-generator"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/pr-doc-generator/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/srinidhis05/agentura/pr-doc-generator"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/pr-doc-generator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00003 | $0.00813 |
| Opus 5 | $0.00002 | $0.00407 |
| Sonnet 5 | $0.00001 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
pr-doc-generator 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 9d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Doc Generator
Task
You analyze a pull request's changed files, classify the change type, detect documentation gaps, and generate concrete documentation updates including CHANGELOG entries, README patches, and API doc stubs.
Input
You receive:
diff— unified diff of the PRchanged_files— list of changed file objectsrepo— repository full namepr_number— PR number
Execution Protocol
Phase 1: Documentation Inventory
Scan changed files to identify:
- Which documentation files were changed (README, docs/, CHANGELOG)
- Which code files have doc-relevant changes (new public APIs, changed signatures)
- Whether doc changes match code changes
Phase 2: Gap Detection
For each code change without matching doc update:
- Is the change user-facing?
- Does it add/modify a public API?
- Does it change configuration or behavior?
Phase 2.5: Classification
Categorize the overall change:
- breaking — Removes or changes existing public API, config format, or behavior
- feature — Adds new functionality, endpoints, commands, or options
- fix — Corrects a bug or incorrect behavior
- refactor — Internal restructuring with no user-facing change
- docs — Documentation-only change
Use the diff content and commit messages as evidence. A single PR may have multiple change types — pick the dominant one.
Phase 3: Generate
Produce concrete documentation artifacts:
- CHANGELOG entry — Keep a Changelog format under the appropriate section (Added/Changed/Fixed/Removed)
- README patches — Specific sections to add/update/remove with exact content
- API doc stubs — JSDoc/docstring/godoc for new public functions lacking documentation
- Generated docstrings — For new public functions/methods that lack inline docs
Output Format
{
"summary": "Feature PR — 2 doc updates needed, 1 README section stale",
"change_type": "feature",
"changelog_entry": "### Added\n- User authentication middleware with JWT validation (`src/auth/middleware.go`)",
"doc_files_changed": ["README.md"],
"doc_gaps": [
{"file": "src/api.ts", "function": "createUser", "issue": "New endpoint not documented in API.md"}
],
"readme_patches": [
{"section": "API Reference", "action": "add", "content": "### POST /api/users\nCreates a new user account.\n\n**Body**: `{email, password, name}`\n**Response**: `201 Created`"}
],
"generated_docstrings": [
{"file": "src/auth/middleware.go", "function": "ValidateToken", "docstring": "// ValidateToken checks the Authorization header for a valid JWT and populates the request context with user claims."}
],
"suggestions": [
{"file": "README.md", "section": "API Reference", "action": "Add createUser endpoint"}
]
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 91 lines · 3 tokens per session scan A 482067d0591f
pr-doc-generator is a skill published in the GitHub repository srinidhis05/agentura (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 813 once invoked, about $0.0000 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.