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 skills add kaustubhhiware/agent-skills-fullstack-development --skill writing-stylegit clone --depth 1 https://github.com/kaustubhhiware/agent-skills-fullstack-developmentWrote 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/kaustubhhiware/agent-skills-fullstack-development/writing-style)<a href="https://agentmods.dev/skills/kaustubhhiware/agent-skills-fullstack-development/writing-style"><img src="https://agentmods.dev/badge/skills/kaustubhhiware/agent-skills-fullstack-development/writing-style/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/skills/kaustubhhiware/agent-skills-fullstack-development/writing-style"><img src="https://agentmods.dev/badge/skills/kaustubhhiware/agent-skills-fullstack-development/writing-style.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.00023 | $0.00505 |
| Opus 5 | $0.00012 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
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 9d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Style Guidelines
Personal writing preferences for blog posts and technical documents.
1. Bold Usage
Use sparingly. Bold is for emphasis, not decoration.
- Don't bold every bullet point
- Don't bold "important" words throughout paragraphs
- Reserve bold for truly critical terms or section titles
2. Em-Dash Rules
Only for removable parenthetical phrases. Not for dramatic effect.
Format: -- (double hyphen), not — (unicode em-dash)
Valid:
I slept for very long last night -- although with no good quality -- and still woke up tired
Invalid:
This is important -- and it changes everything
The results were clear -- success
Test: If you can't remove the content between dashes without losing core meaning, don't use em-dashes.
3. Banned Sentence Patterns
Avoid these dramatic/superlative constructions:
- "That's not just X, that's Y -- that's Z"
- "This is the testament to X: that this is Y"
- "I strive to get better not just for X, but for Y that I want to Z"
- "This isn't merely X; it's fundamentally Y"
- Starting sentences with "The key insight here is that..."
- "What makes this particularly interesting is..."
4. Tone Guidelines
- Conversational but technical
- First-person narrative where appropriate
- Honest about uncertainties and WIP status
- Questions-driven structure can be used (pose questions, then answer them - but try to use first-person narrative or a monologue tone)
- No excessive validation or superlatives
- No hedging qualifiers ("quite", "rather", "fairly")
5. Technical Writing
- Include code examples with tensor shapes when relevant
- Use
> Note:blockquotes for asides - Footnotes for paper references
- Concrete numbers over vague statements
- Every claim should be traceable to a commit or doc or a reference link
6. Structure
- Numbered sections with H2 headers
- Lists for enumerable items
- Horizontal rules between major sections
These guidelines are working if: text reads naturally, emphasis is meaningful, and technical content is precise without being dry.
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.
- 9d ago First seen · 77 lines · 23 tokens per session scan A 579ca88492ba
writing-style is a skill published in the GitHub repository kaustubhhiware/agent-skills-fullstack-development (16 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 505 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…