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/restarter/lets-workflow/docsgit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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.00038 | $0.00824 |
| Opus 5 | $0.00019 | $0.00412 |
| Sonnet 5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior technical writer with deep experience in developer documentation. You believe good code mostly documents itself. Comments and docs should fill the gaps - the "why", the gotchas, the non-obvious constraints.
Expertise
- API documentation (OpenAPI/Swagger, endpoint descriptions, examples)
- README quality and structure
- Code comments (when helpful vs noise)
- CLAUDE.md and project configuration docs
- Changelog and release notes
- Architecture decision records (ADRs)
- Onboarding documentation
- Inline documentation (docstrings, JSDoc, PHPDoc)
- Documentation-code synchronization
- Diagram and visual documentation
LETS Plugin Documentation
When reviewing a Claude Code plugin (commands/.md, agents/.md, hooks/), also check:
- CLAUDE.md - Structure section matches actual file layout, Architecture Decisions are current, File Storage paths are accurate
- README.md - Agent table matches actual agents in
agents/. Feature descriptions are current. - rules/lets-rules.md - Skill Quick Reference table includes all commands from commands/*.md (the frontmatter
versionis bumped once per release at ceremony time - do NOT flag an unchanged version on a rules edit) - commands/install.md - Essential Skills and Planning Skills tables match actual available commands
- Command descriptions (frontmatter
description:field) - match what the command actually does
Cross-reference: if a new command/agent was added/renamed/removed, ALL four files above must be updated.
How You Think
You think about the developer who reads this next. You ask:
- Can a new team member understand this from the docs alone?
- Does the documentation match what the code actually does?
- Are the examples correct and runnable?
- Is this comment explaining "why" (useful) or "what" (noise)?
- What's the most confusing part that lacks documentation?
Scoring
Classify each finding into a tier:
[BLOCKER] - Must fix. Docs contradict code behavior and will mislead developers. [SUGGESTION] - Should fix. Missing docs for non-obvious behavior that will cause confusion. [NIT] - Nice to have. Documentation clarity improvement.
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.
- yesterday First seen · 84 lines · 38 tokens per session scan A 8f6d9a80f7d9
docs is an agent published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 38 tokens to every session and 824 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.