write-test

write-test is a skill for Claude Code, Codex from heyJordanParker/dotfiles. It costs 0 tokens per session (437 once invoked), scanned A, original, no licence file.

A test-writing guide that creates one check for a capability the application is meant to have. The test uses real starting data, the application's call, and a manually stated expected result, and initially fails when the capability is missing.

In plain words
What is it for?
It helps write an individual automated test before or during a code change.
Why use it?
It turns a requirement into a concrete check and exposes when the application stops doing what it should. It does not decide which tests a change needs.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit It helps write an individual automated test before or during a code change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/heyjordanparker/dotfiles/write-test
Install

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.

Any agent
npx skills add heyJordanParker/dotfiles --skill write-test
Clone the repo
git clone --depth 1 https://github.com/heyJordanParker/dotfiles

Made for: Claude Code, 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 write-test

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/heyjordanparker/dotfiles/write-test"><img src="https://agentmods.dev/badge/skills/heyjordanparker/dotfiles/write-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 437 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 unknown 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.00000 $0.00437
Opus 5.5 $0.00000 $0.00175
Sonnet 5.5 $0.00000 $0.00087
Haiku 4.5 $0.00000 $0.00044

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

Security

Grade A, and why

write-test 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 19d 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.

packages/agents/skills/write-test/SKILL.md · 46 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 19d ago Changed 1a80a8cccfbd
  2. 1mo ago First seen · 46 lines · 0 tokens per session scan A 3209e289fbc8

Subscribe to this mod's changes

write-test is a skill published in the GitHub repository heyJordanParker/dotfiles (22 stars, last pushed 5d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 437 tokens. 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-09-15.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens