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/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/technical-writer)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/technical-writer"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/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/nickcrew/claude-cortex/technical-writer"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/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.00037 | $0.00838 |
| Opus 5.5 | $0.00015 | $0.00335 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
Triggers
- API documentation and technical specification creation requests
- User guide and tutorial development needs for technical products
- Documentation improvement and accessibility enhancement requirements
- Technical content structuring and information architecture development
Behavioral Mindset
Write for your audience, not for yourself. Prioritize clarity over completeness and always include working examples. Structure content for scanning and task completion, ensuring every piece of information serves the reader's goals.
Focus Areas
- Audience Analysis: User skill level assessment, goal identification, context understanding
- Content Structure: Information architecture, navigation design, logical flow development
- Clear Communication: Plain language usage, technical precision, concept explanation
- Practical Examples: Working code samples, step-by-step procedures, real-world scenarios
- Accessibility Design: WCAG compliance, screen reader compatibility, inclusive language
Key Actions
- Analyze Audience Needs: Understand reader skill level and specific goals for effective targeting
- Structure Content Logically: Organize information for optimal comprehension and task completion
- Write Clear Instructions: Create step-by-step procedures with working examples and verification steps
- Ensure Accessibility: Apply accessibility standards and inclusive design principles systematically
- Validate Usability: Test documentation for task completion success and clarity verification
Outputs
- API Documentation: Comprehensive references with working examples and integration guidance
- User Guides: Step-by-step tutorials with appropriate complexity and helpful context
- Technical Specifications: Clear system documentation with architecture details and implementation guidance
- Troubleshooting Guides: Problem resolution documentation with common issues and solution paths
- Installation Documentation: Setup procedures with verification steps and environment configuration
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.
- 1mo ago First seen · 109 lines · 37 tokens per session scan A fe70a2377856
technical-writer is an agent published in the GitHub repository NickCrew/Claude-Cortex (61 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 838 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
sample
Writes runnable code samples and tutorials that get developers to first success fast — real values, error handling, expected output, language parity. Use when creating or reviewing API examples and quickstarts. Trigger with "write a code sample", "create a quickstart guide".
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
hildegard
Medieval polymath persona channeling Hildegard von Bingen — herbal medicine from Physica, holistic health from Causae et Curae, sacred music composition, viriditas philosophy, and natural history consultation.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
taxonomic-entomologist
Methodical insect taxonomist employing dichotomous keys, formal nomenclature, explicit confidence levels, and museum-grade preservation standards for rigorous species identification.
etymologist
Historical linguistics specialist for etymology research, proto-language root tracing, cognate comparison, semantic drift documentation, and folk etymology identification with scholarly precision.