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 agents/sjungling/sjungling-claude-plugins/generate-docsgit clone --depth 1 https://github.com/sjungling/sjungling-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/agents/sjungling/sjungling-claude-plugins/generate-docs)<a href="https://agentmods.dev/agents/sjungling/sjungling-claude-plugins/generate-docs"><img src="https://agentmods.dev/badge/agents/sjungling/sjungling-claude-plugins/generate-docs.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.1 | $0.00050 | $0.00964 |
| Opus 5 | $0.00025 | $0.00482 |
| Sonnet 5 | $0.00010 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
generate-docs 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build symbol graph documentation for the current Xcode project and make it discoverable to future LLM sessions. The dispatching command will provide context including the plugin root path and optional scheme argument.
For the visual workflow diagram, see ./references/generate-docs-workflow.mmd relative to the plugin commands directory.
Step 1: Run generate-docs.sh
Execute the helper script which handles scheme discovery, docbuild, symbol graph extraction, and transformation to structured CSVs:
bash <plugin-root>/commands/references/generate-docs.sh [scheme]
- The
<plugin-root>path and optional scheme argument will be provided by the dispatching command
The script outputs one JSON line per step with the structure: {"step": "...", "status": "...", "output": "..."}.
Step 2: Handle Results
Parse the JSON output from the script:
- preflight step: If
statusis"error", report the error and stop - scheme step: If
statusis"error", report available schemes and stop - docbuild step: If
statusis"error", report the build error and suggest running/build-and-runfirst to fix compilation issues - extract step: If
statusis"warning", report the warning and stop (no symbol graphs to transform) - transform step: If
statusis"error", report the transform error and stop - summary step: Extract
modules,types,methods,relationshipscounts from the output object
Step 3: Update .gitignore
Check if .gitignore exists in the project root:
- If
.gitignoredoesn't exist, create it - Check if
.build/is already covered (which would include all subdirectories) - If not, check for
.build/api-docs/,.build/docs/, and.build/symbol-graphs-raw/individually - Append any missing entries
Do NOT add a blanket .build/ entry — the project may manage that differently.
Step 4: Update CLAUDE.md
Check if CLAUDE.md exists in the project root. If not, create it.
Search for the marker <!-- generate-docs --> in CLAUDE.md:
- If found, replace everything from
<!-- generate-docs -->to<!-- /generate-docs -->(inclusive) with the block below - If not found, append the block below to the end of CLAUDE.md
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.
- 6d ago First seen · 86 lines · 50 tokens per session scan A 5c58740a1776
generate-docs is an agent published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 23d ago), licensed MIT. It adds 50 tokens to every session and 964 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.