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 agentmods add instructions/nisus74/humanise/agents-mdgit clone --depth 1 https://github.com/Nisus74/humaniseWrote 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/instructions/nisus74/humanise/agents-md)<a href="https://agentmods.dev/instructions/nisus74/humanise/agents-md"><img src="https://agentmods.dev/badge/instructions/nisus74/humanise/agents-md.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 | $0.00411 | $0.00411 |
| Opus 5 | $0.00205 | $0.00205 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
humanise AGENTS.md 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 3d 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.
What it actually says
AGENTS.md
This repo is a writing skill, not an app. If you are an AI coding agent (Codex and others read this file), apply the humanise skill whenever you write or edit prose for the user: commit-message bodies aside, anything human-facing (READMEs, docs, posts, emails, PR descriptions).
How to use it:
- Read
skill/SKILL.mdfor the workflow (assess, draft from the user's corpus, two-pass sweep, self-critique, verify). - Read the user's
skill/profile/(theirsoul.md,voice-fingerprint.md,absolute-rules.md) if present. If there's noprofile/, tell the user to followdocs/getting-started.mdand fall back to the engine defaults. - Run the checker on anything substantial:
python3 skill/evals/assertions/writing_checks.py <draft-file> <dialect> [medium].
The rules in skill/references/ are the shared engine; the voice in skill/profile/ is the user's. Don't apply the prose sweep to code, config, or quoted material (see the "When to apply, and when to hold off" section in skill/SKILL.md).
Engine changes clear the acceptance gate in skill/evals/self-harness-loop.md, runnable end to end via /humanise improve. Never tune a change against skill/evals/holdout-evals.json (reserved held-out), and treat skill/profile/learning/ as soul: the user's verbatim edit history, never committed.
Launch documentation
- Never invent testimonials, metrics or compatibility claims.
- Keep privacy language technically precise. Separate what Humanise stores locally from what the selected AI host may receive under its own data policy.
- Do not change the engine during a launch-surface task.
- Run
npm run qualitybefore completion. - Do not add dependencies without explicit approval.
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.
- 3d ago First seen · 23 lines · 411 tokens per session scan A e65c595c69d7
humanise AGENTS.md is an instructions file published in the GitHub repository Nisus74/humanise (1 stars, last pushed 6d ago), licensed MIT. It adds 411 tokens to every session, about $0.0021 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 instructions, from other repositories
humanizer AGENTS.md
Instructions for blader/humanizer, covering guide for agents, what this repo contains, key files, rules for changes and writing style.
gortex CLAUDE.md
Claude Code instructions for zzet/gortex, covering gortex, build & test, codebase overview, discovery (read once, then keep using) and llm provider (powers ask and searchsymbols assist: modes).
agent-toolkit AGENTS.md
Instructions for ulises-jeremias/agent-toolkit, covering agents.md — ai agent contract, what this toolkit does, repository structure, operating rules and how to add a skill.
core-ai CLAUDE.md
Instructions for helius-labs/core-ai, covering core ai, compiler-managed sync, mcp server pin, skill versioning and router surface maintenance.
ChatCrystal AGENTS.md
Instructions for ZengLiangYi/ChatCrystal, covering agents.md, project overview, commands, development (server port 3721 + client port 13721) and build for production.
core-ai AGENTS.md
Instructions for helius-labs/core-ai, covering core ai — agent instructions, repository overview, mcp server setup, api key setup and public tool surface.