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 commands/syedomershah99/being-human/writegit clone --depth 1 https://github.com/Syedomershah99/being-humanWrote 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/commands/syedomershah99/being-human/write)<a href="https://agentmods.dev/commands/syedomershah99/being-human/write"><img src="https://agentmods.dev/badge/commands/syedomershah99/being-human/write.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.00014 | $0.00409 |
| Opus 5 | $0.00007 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
write 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
Write this in their voice: $ARGUMENTS
Load first. Read .being-human/voiceprint.md before drafting anything. If it
doesn't exist, run /being-human:learn first — don't draft from your defaults and
call it their voice.
Pay attention to ## notes as much as the measured sections. The numbers give
you form; the notes give you what they'd actually say.
Pick the register. Most voiceprints have two. A quick reply and a considered piece are different modes of the same person. Match the one this situation calls for rather than the average.
Draft. Hit the burstiness ratio deliberately — it's the strongest single tell and the easiest to miss, because even prose reads fine to you. Use their vocabulary. Avoid the words on the personal avoid list.
Score it before showing it:
python3 scripts/slopscore.py <draft> --in .being-human/
Revise and re-score until it clears 85, or until what's left is a deliberate choice you can defend. Then show them the draft and the score together.
Do not hand over an unscored draft. The whole point is that self-assessment doesn't work here — generated prose reads fluent to the thing that generated it.
the line
Match the voice. Never bend a fact to fit it.
Don't invent an anecdote because the voice would carry one. Don't add a number you don't have because specifics score better than abstractions. Don't claim an experience they haven't described to you.
When the voice wants a concrete detail and you don't have one, ask for it. A convincing voice wrapped around a fabricated fact is worse than generic prose, because generic prose doesn't get believed.
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 · 47 lines · 14 tokens per session scan A 30ce4d353597
write is a command published in the GitHub repository Syedomershah99/being-human (0 stars, last pushed 21d ago), licensed MIT. It adds 14 tokens to every session and 409 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.