Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/unique-divine/jiyuu/writing-tech)<a href="https://agentmods.dev/skills/unique-divine/jiyuu/writing-tech"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/writing-tech.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.00086 | $0.00976 |
| Opus 5 | $0.00043 | $0.00488 |
| Sonnet 5 | $0.00017 | $0.00195 |
| Haiku 4.5 | $0.00009 | $0.00098 |
Grade A, and why
writing-tech 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 7d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Tech
Use this skill to write and edit clear technical documentation for engineers and agents. Prioritize project-specific clarity over generic style rules.
Core stance
- Write for readers who navigate code, schemas, databases, APIs, commands, services, and operational systems.
- Make the entity type clear when referring to code-formatted symbols.
- Be concise, but don't let brevity create ambiguity.
- Treat these as guidelines, not rigid laws. Depart from them when doing so improves the document.
Qualify code symbols with entity type
When referencing a named code, data, or tool symbol in prose, include a nominal qualifier that identifies what kind of entity it is.
Backticks identify the exact symbol. The surrounding noun tells the reader what the symbol is.
Prefer:
- table
stats_perp_by_user - database column
market_id - GraphQL field
volume - GraphQL type
PerpBorrowing - function
Delegation - agent skill
nibiru-cli-nibid - command
just fmt - REST endpoint
GET /dexpal/v1/stats - file
graphql/graph/perp.graphqls - service
StatsRefresher
Avoid bare references when the entity type is not obvious:
stats_perp_by_userrefreshesDelegationhandles this- use
nibiru-cli-nibid - run
just fmt
Better:
- table
stats_perp_by_userrefreshes - function
Delegationhandles this - use agent skill
nibiru-cli-nibid - run command
just fmt
How strict to be
- Prefer qualifiers on first use in a section, like defining a term or spelling out an abbreviation before using it freely.
- In specs, lean toward qualifying symbols more often than not.
- Relax the rule when repeated qualifiers make a paragraph noisy and the entity type is already clear.
- Use judgment. The goal is unambiguous technical prose, not mechanical repetition.
- Abbreviations are fine in drafts and working notes:
proc,fn,func,db column, andGQL fieldare acceptable when they improve flow. - If the user asks for a polished style or says not to use abbreviations, prefer fuller labels like SQL procedure, function, database column, and GraphQL field.
What ships with it
1 file 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.
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.
- 7d ago First seen · 114 lines · 86 tokens per session scan A 8b0e9569bf45
writing-tech is a skill published in the GitHub repository Unique-Divine/jiyuu (6 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 976 once invoked, about $0.0004 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
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
migrate-goldmark-app-v1-to-v2
Migrate your application from goldmark v1 to v2.
jwx-guide-v4
Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse/sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid the common footguns. For developers using jwx, not for developing the library itself.
readme-generate
A tool that analyzes source code to generate English and Chinese README files and related project documentation.
search-suitable-public-api
Search the curated Agenvoy public API list for an API that fits the current user need or skill context, then chain into the api-tool-add skill to register it under /.config/agenvoy/tools/api/. Triggers when the agent lacks a tool for a data lookup (weather, currency, geocoding, dictionary, etc.), when the user says…