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/aaddrick/claude-pipeline/write-docblocksnpx skills add aaddrick/claude-pipeline --skill write-docblocksgit clone --depth 1 https://github.com/aaddrick/claude-pipelineWrote 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/aaddrick/claude-pipeline/write-docblocks)<a href="https://agentmods.dev/skills/aaddrick/claude-pipeline/write-docblocks"><img src="https://agentmods.dev/badge/skills/aaddrick/claude-pipeline/write-docblocks.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.00031 | $0.00875 |
| Opus 5 | $0.00015 | $0.00438 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
write-docblocks 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Docblocks
Overview
Batch-process PHPDoc documentation gaps by running composer docs:coverage:missing and dispatching parallel phpdoc-writer subagents.
Core principle: Process files in batches of 5 subagents for efficient parallel documentation without overwhelming the system.
When to Use
- Documentation coverage below target (80% classes, 75% methods)
- After creating multiple new services, controllers, or models
- When
composer docs:coverage:missingshows many files needing docs - User requests batch PHPDoc writing
Workflow
digraph write_docblocks {
rankdir=TB;
start [label="Run composer docs:coverage:missing" shape=box];
parse [label="Parse output for file paths" shape=box];
check [label="Files remaining?" shape=diamond];
batch [label="Take next 5 files" shape=box];
dispatch [label="Dispatch 5 phpdoc-writer\nsubagents in parallel" shape=box];
wait [label="Wait for batch to complete" shape=box];
done [label="Run composer docs:coverage\nto verify improvement" shape=box];
start -> parse -> check;
check -> batch [label="yes"];
check -> done [label="no"];
batch -> dispatch -> wait -> check;
}
Execution Steps
1. Get Missing Files
composer docs:coverage:missing 2>&1 | sed 's/\x1b\[[0-9;]*m//g' | grep '\.php$'
This strips ANSI codes and extracts just file paths like:
Console/Commands/ProcessDataCommand.php
Http/Controllers/AuthController.php
Services/AuthService.php
2. Process in Batches of 5
For each batch of 5 files, dispatch phpdoc-writer subagents in parallel using a single message with multiple Task tool calls:
Task(subagent_type="phpdoc-writer", prompt="Write PHPDoc blocks for app/Console/Commands/ProcessDataCommand.php - read the file, understand its purpose, and add comprehensive docblocks for the class and all undocumented methods.")
Task(subagent_type="phpdoc-writer", prompt="Write PHPDoc blocks for app/Http/Controllers/OAuthController.php - read the file, understand its purpose, and add comprehensive docblocks for the class and all undocumented methods.")
// ... 3 more in same message
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.
- 5d ago First seen · 113 lines · 31 tokens per session scan A 6dac5886c3e7
write-docblocks is a skill published in the GitHub repository aaddrick/claude-pipeline (128 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 875 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
laravel-actions
Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions. Use when implementing reusable action classes (object/controller/job/listener/command), converting service classes/controllers/jobs into actions, orchestrating workflows via faked actions, or debugging action entrypoints and wiring.
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
laravel-security
Laravel security best practices for authn/authz, validation, CSRF, mass assignment, file uploads, secrets, rate limiting, and secure deployment.
integration-fixture
Create or validate a .test integration fixture under tests/php/Integration/Fixtures.
create-module
Scaffold a new Marko module — a self-contained Composer package with composer.json, namespaced src/, and Pest tests. Use this skill whenever the user asks to create, add, or scaffold a new Marko module or package. Concrete triggers: 'create a module named payment', 'scaffold an acme/blog package', 'add a new module…