monorepo: Skill for Codex

.agents/skills/technical-writing/SKILL.md

technical-writing is a skill for Codex from lootlog/monorepo. It costs 43 tokens per session (263 once invoked), scanned A, original, MIT.

A set of rules for writing technical documents and development messages clearly, including READMEs, design records, pull requests, release notes, and commit messages.

In plain words
What is it for?
It helps write tutorials, how-to guides, reference pages, explanations, issue briefs, changesets, pull request text, and Conventional Commit messages.
Why use it?
It helps engineers understand documentation quickly and avoids unclear wording, missing context, and unsupported claims.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is lootlog/monorepo's own configuration. It tells Codex how to work on monorepo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything monorepo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lootlog/monorepo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/lootlog/monorepo/main/.agents/skills/technical-writing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/lootlog/monorepo

Made for: Codex.

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.

agentmods badge for technical-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/lootlog/monorepo/technical-writing/github.svg)](https://agentmods.dev/skills/lootlog/monorepo/technical-writing)
Your own site
<a href="https://agentmods.dev/skills/lootlog/monorepo/technical-writing"><img src="https://agentmods.dev/badge/skills/lootlog/monorepo/technical-writing/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.

agentmods 80×15 button for technical-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/lootlog/monorepo/technical-writing"><img src="https://agentmods.dev/badge/skills/lootlog/monorepo/technical-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 263 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00263
Opus 5.5 $0.00017 $0.00105
Sonnet 5.5 $0.00009 $0.00053
Haiku 4.5 $0.00004 $0.00026

Measured 1mo ago against content hash ec86d5ece2ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

technical-writing 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 1mo 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.

.agents/skills/technical-writing/SKILL.md · 32 lines

What it actually says

Technical writing

Write for a tired engineer who needs the point quickly.

Pick the document mode

  • Tutorial: teach by producing visible results.
  • How-to: give steps toward a concrete goal.
  • Reference: state complete facts for lookup.
  • Explanation: explain bounded context, rationale, and trade-offs.

Do not mix modes when separate linked documents would be clearer.

Write

  • Use the repository's real symbols, paths, flags, commands, and domain terms.
  • Put conditions before actions. Write instructions as commands.
  • Prefer active voice, plain words, and one main thought per sentence.
  • Cut filler, vague attribution, promotional language, and claims without evidence.
  • Use numbered lists for sequences and bullets for unordered items.
  • Keep headings in sentence case.
  • State expected output or observable success for procedural steps.
  • Write PR titles, PR descriptions, and Changeset summaries in English.
  • Follow Conventional Commits for commit messages.

Apply the unslop skill as the final editing pass. Preserve required legal, API, and domain terminology.

Files

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.

Changes

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.

  1. 1mo ago First seen · 32 lines · 43 tokens per session scan A ec86d5ece2ff

Subscribe to this mod's changes

technical-writing is a skill published in the GitHub repository lootlog/monorepo (29 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 263 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

plan-update

Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.

react/react · 44 tokens

google-apps-script

Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…

jezweb/claude-skills · 89 tokens

build-with-simplepdf

Integrate SimplePDF into a web application for PDF viewing, editing, filling, signing, programmatic control, AI-agent interaction, human-in-the-loop form prefilling, submissions, webhooks, or customer-controlled storage. Use when a developer wants to add or improve PDF workflows in React, Next.js, JavaScript…

SimplePDF/simplepdf-embed · 103 tokens

edit-pdf

Edit and fill PDF documents. Use when the user wants to fill a PDF form, add text/signatures/checkboxes/images to a PDF, or annotate a PDF. Accepts a PDF URL or file upload and returns a ready-to-use editor link. URL inputs are passed through directly. File uploads are stored temporarily (24 hours) then deleted.

SimplePDF/simplepdf-embed · 74 tokens

widget-authoring

Author or edit ThinkEx widgets, which are self-contained interactive HTML blocks inside documents. Use when the user explicitly asks for a widget, asks for interaction or live computation, or wants a document visual that ordinary blocks cannot express.

ThinkEx-OSS/thinkex · 49 tokens

job-match-standards

How real ATS (Workday/Greenhouse/Lever/Taleo/iCIMS/Ashby) parse, score and rank in 2026; evidence-based matching; and the legal limits on automated screening (EU AI Act high-risk, NYC LL144, EEOC Title VII, GDPR Art. 22). Load for changes under commands/matchresume.rs, coverletter.rs, validate/, documents/embed.

saeedkolivand/ai-job-hunter-app · 88 tokens