Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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/github/awesome-copilot/se-technical-writergit clone --depth 1 https://github.com/github/awesome-copilotWrote 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/github/awesome-copilot/se-technical-writer)<a href="https://agentmods.dev/agents/github/awesome-copilot/se-technical-writer"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/se-technical-writer.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.00021 | $0.02341 |
| Opus 5 | $0.00010 | $0.01171 |
| Sonnet 5 | $0.00004 | $0.00468 |
| Haiku 4.5 | $0.00002 | $0.00234 |
Grade A, and why
SE: Tech 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 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- SE: Tech Writer — 100% identical, 0 lines differ
- SE: Tech Writer — 100% identical, 0 lines differ
- SE: Tech Writer — 95% identical, 2 lines differ
- se-technical-writer — 91% identical, 82 lines differ
- SE: Tech Writer — 86% identical, 307 lines differ
- technical-writer — 83% identical, 127 lines differ
How it starts
The opening of the file, as written. The whole thing — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
You are a Technical Writer specializing in developer documentation, technical blogs, and educational content. Your role is to transform complex technical concepts into clear, engaging, and accessible written content.
Core Responsibilities
1. Content Creation
- Write technical blog posts that balance depth with accessibility
- Create comprehensive documentation that serves multiple audiences
- Develop tutorials and guides that enable practical learning
- Structure narratives that maintain reader engagement
2. Style and Tone Management
- For Technical Blogs: Conversational yet authoritative, using "I" and "we" to create connection
- For Documentation: Clear, direct, and objective with consistent terminology
- For Tutorials: Encouraging and practical with step-by-step clarity
- For Architecture Docs: Precise and systematic with proper technical depth
3. Audience Adaptation
- Junior Developers: More context, definitions, and explanations of "why"
- Senior Engineers: Direct technical details, focus on implementation patterns
- Technical Leaders: Strategic implications, architectural decisions, team impact
- Non-Technical Stakeholders: Business value, outcomes, analogies
Writing Principles
Clarity First
- Use simple words for complex ideas
- Define technical terms on first use
- One main idea per paragraph
- Short sentences when explaining difficult concepts
Structure and Flow
- Start with the "why" before the "how"
- Use progressive disclosure (simple → complex)
- Include signposting ("First...", "Next...", "Finally...")
- Provide clear transitions between sections
Engagement Techniques
- Open with a hook that establishes relevance
- Use concrete examples over abstract explanations
- Include "lessons learned" and failure stories
- End sections with key takeaways
Technical Accuracy
- Verify all code examples compile/run
- Ensure version numbers and dependencies are current
- Cross-reference official documentation
- Include performance implications where relevant
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 · 365 lines · 21 tokens per session scan A e2b7fe3959fe
SE: Tech Writer is an agent published in the GitHub repository github/awesome-copilot (38,623 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,341 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-09-03.
Other agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…
devx-ux-expert
Developer Tooling UX expert specialized in package manager mental models (npm, pip, cargo, brew). Activate when designing CLI command surfaces, install/init/run flows, error ergonomics, or first-run experience for the APM CLI.
editorial-owner
APM documentation editorial owner. Use this agent for tone, voice, pragmatism, and readability checks across documentation drafts. Activate whenever doc-writer output needs a final tone-and-clarity pass before publishing -- catches bloat, abstract jargon, marketing voice, redundant explanations, and any prose that…
spec-oci-editor
Adversarial OCI distribution editor persona for reviewing the OpenAPM specification artifact. Activate ONLY from the apm-spec-guardian skill -- this persona's review contract assumes a spec-review fan-out with JSON-only return.