Borrowing it
Nothing to install: this file belongs to hwillGIT/library-of-context. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hwillGIT/library-of-context/main/.agents/skills/write-timeless-technical-prose/SKILL.mdgit clone --depth 1 https://github.com/hwillGIT/library-of-contextWrote 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/hwillgit/library-of-context/write-timeless-technical-prose)<a href="https://agentmods.dev/skills/hwillgit/library-of-context/write-timeless-technical-prose"><img src="https://agentmods.dev/badge/skills/hwillgit/library-of-context/write-timeless-technical-prose.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.00116 | $0.01934 |
| Opus 5 | $0.00058 | $0.00967 |
| Sonnet 5 | $0.00023 | $0.00387 |
| Haiku 4.5 | $0.00012 | $0.00193 |
Grade A, and why
write-timeless-technical-prose 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 5d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Timeless, Non-Historical Technical Prose
Write the artifact as a coherent description of the system, not as a record of the conversation or editing process that produced it. The result must read as one coherent editorial present.
Establish the document's job
Classify the material before editing:
- Use explanatory documents for mechanisms, interfaces, constraints, rationale, and failure behavior.
- Use
CHANGELOGfor completed change history. - Use status and roadmap documents for capability state, sequence, and planned work.
- Use migration and compatibility sections for version transitions that affect safe operation.
- Use citations for publication and access dates.
Keep time-relative language only when time, version, or runtime state is part of that job.
Write in one editorial present
- State the mechanism or contract directly.
- State the reason only when it explains behavior, a constraint, or a trade-off.
- Remove narration about the prompt, requester, author, drafting process, review process, or sequence of edits.
- Remove release-relative words such as "now," "currently," "previously," "recently," "new," "updated," and "latest" when the sentence remains true without them.
- Remove temporal provenance. Do not tell readers when content entered the artifact. State the complete structure and behavior directly.
- Move necessary history to a changelog, status page, ADR, migration note, or labeled benchmark record.
- Preserve precise runtime terms such as "current request," "recent ring," "new snapshot," and "previous desk" when they distinguish live states in an algorithm.
Do not use phrases that show placement or edit history. Examples include "the section added below," "the new module," and "after the refactor." Name the component and state its contract. Use sequence words only for a technical order. Examples include a procedure, runtime transition, dependency, migration, or evaluation protocol.
Replace process commentary with technical content
What ships with it
5 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.
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.
- 5d ago First seen · 206 lines · 116 tokens per session scan A f7e9ee3f999f
write-timeless-technical-prose is a skill published in the GitHub repository hwillGIT/library-of-context (0 stars, last pushed 15d ago), licensed MIT. It adds 116 tokens to every session and 1,934 once invoked, about $0.0006 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
image-context-runtime
Use for image-heavy Codex work when generated or inspected media should stay behind a bounded MCP boundary and the controlling task should receive only durable Job IDs, hashes, relative references, and compact text handoffs.
blz-docs-search
Teaches effective documentation search using the blz CLI tool. Use when searching documentation with blz, looking up APIs, finding code examples, retrieving citations, or when questions mention libraries, frameworks, "how to", or documentation topics. Covers BM25 full-text search patterns, citation retrieval, and…
blz-source-management
Teaches how to discover, validate, and add llms.txt documentation sources to the blz CLI. Use when adding documentation to blz, finding llms.txt or llms-full.txt files, validating sources, refreshing content, or managing the documentation index. Covers source discovery, dry-run validation, and index file handling.
astra-vector-backend
Design Astra DB Data API and vector-search backends for retrieval, metadata filtering, and LangChain-compatible stores.
mcp-server-patterns
Build MCP servers with Node and TypeScript using tools, resources, Zod schemas, and stdio transport.
python-patterns
Write maintainable Python packages with type hints, dataclasses, pathlib, and clear module boundaries.