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 skills/kataras/jwt/human-writingnpx skills add kataras/jwt --skill human-writinggit clone --depth 1 https://github.com/kataras/jwtWrote 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/kataras/jwt/human-writing)<a href="https://agentmods.dev/skills/kataras/jwt/human-writing"><img src="https://agentmods.dev/badge/skills/kataras/jwt/human-writing.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.00159 | $0.01899 |
| Opus 5 | $0.00079 | $0.00949 |
| Sonnet 5 | $0.00032 | $0.00380 |
| Haiku 4.5 | $0.00016 | $0.00190 |
Grade A, and why
human-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 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human writing, for the jwt repository
This repository is read by people deciding whether to trust a security library with their authentication. It has to sound like an engineer wrote it, because one did. Prose that reads as generated invites the question of whether the code was too.
This skill is the standard, and scripts/scan-tells.ps1 is the check.
Scope
Every tracked markdown file: book/**.md, brand/BRAND.md, skill/**/*.md including this
one, and the root README.md and CHANGELOG.md. That is exactly the set the scanner's
-Md mode walks, so if the two disagree, one of them has a bug.
Untracked files are out of scope whatever they contain. Local agent configuration is not published, so holding it to a standard no reader will ever see is wasted effort.
Doc comments in .go files are in scope for the standard but not for the scanner. The
scanner skips Go entirely, because separating a doc comment from a string literal from a
code sample inside a comment is more machinery than it is worth. Those are edited by hand,
and the rules below still apply to them.
book/output/ is generated. Never edit it.
book/README.md, the preface, is the reference voice. When you are unsure how a sentence
should sound, read it.
Scan before you write, and again after
pwsh skill/human-writing/scripts/scan-tells.ps1 book/03-claims.md
pwsh skill/human-writing/scripts/scan-tells.ps1 -Md # the whole corpus
pwsh skill/human-writing/scripts/scan-tells.ps1 -Md -Summary # counts per rule
pwsh skill/human-writing/scripts/scan-tells.ps1 -Wrap book/ # long lines
skill/human-writing/scripts/scan-tells.sh --md --summary # no pwsh needed
The scanner is fence aware. It never reports anything inside a fenced code block, and it blanks inline code spans, link targets and bare URLs before matching, so an identifier or a URL containing a double dash is not a finding. Exit code is 1 while findings remain.
Zero findings is the bar for every file here. There are no correct-in-context em dashes in this repository.
What ships with it
2 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 · 162 lines · 159 tokens per session scan A 7f2709514990
human-writing is a skill published in the GitHub repository kataras/jwt (211 stars, last pushed 14d ago), licensed MIT. It adds 159 tokens to every session and 1,899 once invoked, about $0.0008 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-30.
Other skills, from other repositories
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.
jwx-companion-bulk
Apply bulk operations across all jwx companion modules. Args.
simple-go-api
Teach, explain, review, or extend the vc-gin-api Gin project while preserving its small Router-to-Handler-to-Service-to-DAO flow. Use when a learner asks how a request works, wants to add a field or endpoint, needs a guided Go backend exercise, or asks Codex to check this repository for overengineering. Do not use to…
ddd-go-backend
Build production-ready Go backend services following DDD-layered architecture. Covers project scaffolding, config (Viper), database (GORM + MySQL/PostgreSQL), object storage (S3/MinIO), OAuth2 + JWT auth, OpenTelemetry tracing + Jaeger visualization, Zap logging, middleware patterns, and API routing. Use when creating…
testing-for-json-web-token-vulnerabilities
Test JWT implementations for critical vulnerabilities including algorithm confusion, none algorithm bypass, kid parameter injection, and weak secret exploitation to achieve authentication bypass and privilege escalation.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.