edmunds-claude-code: Agent for Claude Code

.claude/agents/technical-writer.md

technical-writer is an agent for Claude Code from edmund-io/edmunds-claude-code. It costs 20 tokens per session (477 once invoked), scanned A, original, no licence file.

A coding agent for writing technical documentation that is clear and suited to its intended readers.

In plain words
What is it for?
Use it for guides, reference material, explanations, and documentation designed for different audiences.
Why use it?
It helps remove confusion by presenting technical information in an understandable and usable form.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is edmund-io/edmunds-claude-code's own configuration. It tells Claude Code how to work on edmunds-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything edmunds-claude-code configures →

Part of the edmunds-claude-code plugin — 14 commands, 11 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to edmund-io/edmunds-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/edmund-io/edmunds-claude-code/main/.claude/agents/technical-writer.md
Clone the repo
git clone --depth 1 https://github.com/edmund-io/edmunds-claude-code

Made for: Claude Code.

Or install edmunds-claude-code, the plugin that ships this one along with the rest of its 14 commands, 11 agents.

Wrote 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.

agentmods badge for technical-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/edmund-io/edmunds-claude-code/technical-writer.svg)](https://agentmods.dev/agents/edmund-io/edmunds-claude-code/technical-writer)
Your own site
<a href="https://agentmods.dev/agents/edmund-io/edmunds-claude-code/technical-writer"><img src="https://agentmods.dev/badge/agents/edmund-io/edmunds-claude-code/technical-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 477 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00477
Opus 5 $0.00010 $0.00238
Sonnet 5 $0.00004 $0.00095
Haiku 4.5 $0.00002 $0.00048

Measured 8d ago against content hash 956840387cac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 8d 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.

.claude/agents/technical-writer.md · 49 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 8d ago First seen · 49 lines · 20 tokens per session scan A 956840387cac

Subscribe to this mod's changes

technical-writer is an agent published in the GitHub repository edmund-io/edmunds-claude-code (1,505 stars, last pushed 10mo ago), with no licence file. It adds 20 tokens to every session and 477 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

socratic-mentor

Educational guide specializing in Socratic method for programming knowledge with focus on discovery learning through strategic questioning.

SuperClaude-Org/SuperClaude_Framework · 24 tokens

technical-writer

Create clear, comprehensive technical documentation tailored to specific audiences with focus on usability and accessibility.

SuperClaude-Org/SuperClaude_Framework · 20 tokens

code-reviewer

Performs iterative QA review of executed scripts. Verifies code correctness, methodology alignment, validation robustness, and output data quality. Creates parallel QA inspection scripts. Invoked by orchestrator after each Stage 5-8 script execution. Also performs QA review of profiling scripts during Data Onboarding…

brycewang-stanford/Auto-Empirical-Research-Skills · 70 tokens

data-verifier

Performs adversarial goal-backward verification of completed analyses. Verifies artifact existence, substantiveness, wiring, and cross-artifact coherence. Invoked by orchestrator at Stage 12 (Final Review) before delivery.

brycewang-stanford/Auto-Empirical-Research-Skills · 48 tokens

data-ingest

Systematically profiles tabular datasets across four structured parts (Structural, Statistical, Relational, Interpretation), producing detailed findings that feed into skill authoring. Invoked by the orchestrator once per profiling part during Data Onboarding Mode.

brycewang-stanford/Auto-Empirical-Research-Skills · 50 tokens

notebook-assembler

Compiles executed scripts into a Marimo notebook by literally copying script file contents into cells. Does not generate new analysis code, dashboards, or interactive widgets. Invoked at Stage 9 after all Stage 5-8 scripts and QA substages are complete.

brycewang-stanford/Auto-Empirical-Research-Skills · 57 tokens