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/YousefNabil-SOC/claude-apexWrote 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/commands/yousefnabil-soc/claude-apex/create-doc)<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/create-doc"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/create-doc.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.1 | $0.00000 | $0.00235 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
create-doc 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.
What it actually says
Generate a professional Word document (.docx) using Python and python-docx.
The user will provide: document type (proposal/report/contract/NDA/brief/memo), content, and output filename.
Steps:
- Ask for: document type, title, sections/content, output filename
- Generate a Python script using python-docx that creates a complete document with:
- Cover page with title, date, client/company name
- Proper heading hierarchy (Heading 1, 2, 3)
- Body text with professional formatting
- Tables where appropriate
- Page numbers and footer
- For legal docs: numbered clauses, definitions section, signature block
- Run the script with Bash to produce the .docx file
- Confirm the output file path
Supported document types:
- proposal: executive summary, scope, timeline, pricing, terms
- contract/NDA: parties, definitions, obligations, terms, signatures
- report: executive summary, findings, recommendations, appendix
- brief: background, objective, approach, deliverables
- memo: to/from/date/re header, body, action items
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.
- 8d ago First seen · 23 lines · 0 tokens per session scan A 89d7af921c74
create-doc is a command published in the GitHub repository YousefNabil-SOC/claude-apex (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 235 tokens. 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 commands, from other repositories
doc-gen
Generate documentation — JSDoc, docstrings, README sections, or API docs.
share
You are sharing personal documents to the team's shared namespace.
test-suite
Run comprehensive test suite with coverage analysis.
security-scan
Run security audit on codebase.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.