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 skills/qte77/claude-code-plugins/generating-writeupnpx skills add qte77/claude-code-plugins --skill generating-writeupgit clone --depth 1 https://github.com/qte77/claude-code-pluginsWhat 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.00035 | $0.01128 |
| Opus 5 | $0.00017 | $0.00564 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
generating-writeup 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writeup Generation
Target: $ARGUMENTS
Generates structured academic/technical writeups as markdown with citation
support. IEEE [1] style by default. PDF export via pandoc is optional.
Workflow
- Parse arguments - Extract topic, template (default:
project-report-IMRaD), and citation style - Create directory -
docs/write-up/<topic>/ - Copy template - Copy from
templates/todocs/write-up/<topic>/:project-report-IMRaD— scientific/academic (Introduction, Methods, Results, Discussion)technical-doc— software documentation (Overview, Architecture, API, Config, Deployment)
- Fill sections - Replace TODO comments in each chapter file
- Setup bibliography - Add entries to
09a_bibliography.bib - Run markdownlint -
npx markdownlint-cli docs/write-up/<topic>/*.md - Generate PDF (optional) - If pandoc is available, run
make pandoc_run
Additional Resources
- Templates: project-report-IMRaD/ | technical-doc/
- Setup help:
make -f $CLAUDE_PLUGIN_ROOT/Makefile setup_pdf_converter HELP - Pandoc help:
make -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run HELP=1
Citation Styles
| Style | CSL File | Notes |
|---|---|---|
| IEEE (default) | Bundled (scripts/writeup/citation-styles/ieee.csl) |
Numeric [1] |
| APA | Bundled (scripts/writeup/citation-styles/apa.csl) |
Author-date (Smith, 2024) |
| Chicago | Bundled (scripts/writeup/citation-styles/chicago-author-date.csl) |
Author-date (Smith 2024) |
Additional CSL files are available from the Zotero Style Repository.
PDF Export (Optional)
If pandoc and LaTeX are installed, generate PDF using the bundled Makefile:
dir=docs/write-up/<topic> && \
make -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run \
INPUT_FILES="$$(printf '%s\036' $$dir/*.md)" \
OUTPUT_FILE="$$dir/output.pdf" \
BIBLIOGRAPHY="$$dir/09a_bibliography.bib"
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- templates/project-report-IMRaD/00_title_abstract_abbrev.tex 1.2 KB
- templates/project-report-IMRaD/01_build_settings.md 114 B
- templates/project-report-IMRaD/02_project_introduction.md 97 B
- templates/project-report-IMRaD/03_desired_state.md 99 B
- templates/project-report-IMRaD/04_planning_and_solution.md 93 B
- templates/project-report-IMRaD/05_implementation.md 85 B
- templates/project-report-IMRaD/06_control_of_success.md 81 B
- templates/project-report-IMRaD/07_results.md 63 B
- templates/project-report-IMRaD/08_summary_outlook.md 80 B
- templates/project-report-IMRaD/09a_bibliography.bib 209 B
- templates/project-report-IMRaD/10_appendices.md 67 B
- templates/project-report-IMRaD/11_index.md 49 B
- templates/technical-doc/01_build_settings.md 101 B
- templates/technical-doc/02_overview.md 75 B
- templates/technical-doc/03_architecture.md 89 B
- templates/technical-doc/04_api.md 93 B
- templates/technical-doc/05_configuration.md 89 B
- templates/technical-doc/06_deployment.md 85 B
- templates/technical-doc/07_troubleshooting.md 87 B
- templates/technical-doc/09a_bibliography.bib 200 B
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 · 105 lines · 0 tokens per session scan A 8e99ad95689c
generating-writeup is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,128 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-31.
Other skills, from other repositories
orchestrator
FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.
flutter-guide
Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.
maestro-flutter
Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
codex-advisor
Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…