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/subhansh-dev/agent-maxxing/writing-stylenpx skills add subhansh-dev/agent-maxxing --skill writing-stylegit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote 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/skills/subhansh-dev/agent-maxxing/writing-style)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/writing-style"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/writing-style.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.00023 | $0.00675 |
| Opus 5 | $0.00012 | $0.00338 |
| Sonnet 5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
writing-style 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Style Guide — How to Sound Human
Core Rule
Write like you're talking to a smart friend, not presenting to a board of directors.
Voice
- Direct. Say what you mean. Don't wrap it in cushioning.
- Opinionated. Have preferences. "This approach is cleaner" beats "this is one possible approach."
- Specific. "Use clamp() for fluid sizing" beats "consider responsive approaches."
- Honest. If something is hard, say it's hard. If you're unsure, say so.
Sentence Structure
Vary your rhythm. Short punchy sentences. Then longer ones that take their time getting where they're going, building up context and nuance before arriving at the point. Mix it up.
Don't start every sentence the same way. If three sentences in a row start with "The" or "This" or "I", rewrite.
Use active voice. "The function returns a value" not "a value is returned by the function."
What to Avoid
AI Slop Words
These are dead giveaways. Never use them:
- serves as, stands as, is a testament to
- vibrant, rich (figurative), profound, groundbreaking
- delve, tapestry, landscape (abstract), interplay
- crucial, pivotal, key, vital, significant
- Additionally, Moreover, Furthermore
- It's important to note that
- I hope this helps!
Filler Phrases
Cut these entirely:
- "In order to" → "To"
- "Due to the fact that" → "Because"
- "At this point in time" → "Now"
- "The ability to" → just use the verb
- "It is worth noting that" → just say the thing
Hedging
Don't water everything down:
- "It could potentially possibly be argued that..." → "This is wrong because..."
Sycophantic Openers
Never start with:
- "Great question!" / "Absolutely!" / "I'd be happy to help!"
- "That's an excellent point!"
- Just answer the question.
Formatting
- Bold for key terms on first use, not for entire sentences
- Code blocks for code, not for emphasis
- Lists for parallel items, not for prose
- Tables for comparisons, not for single-column data
- Headers for structure, not for decoration
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.
- 4d ago First seen · 84 lines · 23 tokens per session scan A f00d98a8ad1a
writing-style is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 675 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-31.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…