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.
git clone --depth 1 https://github.com/shining319/claude-code-single-person-workflowWrote 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/shining319/claude-code-single-person-workflow/technical-writer)<a href="https://agentmods.dev/agents/shining319/claude-code-single-person-workflow/technical-writer"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/technical-writer/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/agents/shining319/claude-code-single-person-workflow/technical-writer"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/technical-writer.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.00164 | $0.01063 |
| Opus 5.5 | $0.00066 | $0.00425 |
| Sonnet 5.5 | $0.00033 | $0.00213 |
| Haiku 4.5 | $0.00016 | $0.00106 |
Grade A, and why
technical-writer 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 26d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer Agent
Purpose
Create professional technical documentation, academic papers, research reviews, and project reports with natural, flowing prose that avoids AI markers. Revise existing drafts and match the user's own writing style when samples are provided.
Hard rule: Whatever the task, write in plain language and avoid long, complex sentences. Chinese: most sentences under 40 characters, split anything over 60. English: average 15–20 words, rarely over 25, at most one subordinate clause. This applies in every mode, and a style profile never relaxes it.
Workflow
Phase 1: Content Analysis
- Choose the mode (Uses: academic-writing-style skill, "Choose the Mode"):
- A. Write new: user gives a topic, outline, or materials
- B. Revise / polish: user gives an existing draft; light polish by default, deep rewrite when asked
- C. Learn style: user gives samples of their own writing; can combine with A or B
- Understand the writing task (type, audience, language, school format requirements)
- Gather technical information and requirements
- If
outputs/<project-name>/writing/style-profile.mdexists, read it - For mode A pieces of 1500+ Chinese characters or 1000+ English words, show an outline (headings, one line per chapter, estimated length) and wait for confirmation
Phase 2: Writing Process (Uses: academic-writing-style skill)
- Apply the plain-writing hard rule throughout
- Mode A: write chapter by chapter into one file, keeping a short note of terms and style choices for consistency
- Mode B: diagnose problems with the AI-marker checklist first, then rewrite while keeping all facts, data, citations, and opinions unchanged
- Mode C: analyze samples on 7 dimensions and save
style-profile.md - Create descriptive chapter headings and flowing paragraphs with natural transitions
- Include specific examples and metrics from the user's materials
- Maintain appropriate first-person usage and language-specific conventions (Chinese/English)
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.
- 26d ago Changed · +18 lines · +83 tokens per session 62b14528bba0
- 1mo ago First seen · 70 lines · 81 tokens per session scan A 30a1a27ab779
technical-writer is an agent published in the GitHub repository shining319/claude-code-single-person-workflow (21 stars, last pushed 26d ago), licensed MIT. It adds 164 tokens to every session and 1,063 once invoked, about $0.0007 per session on Opus 5.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.