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 skills add CodeInfinity1/Stram --skill humanized-writinggit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/humanized-writing)<a href="https://agentmods.dev/skills/codeinfinity1/stram/humanized-writing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/humanized-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.
<a href="https://agentmods.dev/skills/codeinfinity1/stram/humanized-writing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/humanized-writing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.00389 |
| Opus 5.5 | $0.00011 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
humanized-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.
What it actually says
Humanized Writing
Purpose
Make writing feel clear and human without adding fluff or false personality. Preserve the user's intent, facts, and level of formality.
When To Use
Use for emails, docs, posts, scripts, messages, summaries, and rewriting AI-sounding prose.
Inputs And Evidence
- Original text, audience, tone, constraints, and must-keep facts.
- User voice examples when available.
Tool Map
writing_draft_createwriting_draft_inspectdoc-coauthoringinternal-comms-writingsocial-media-draftingwrite_notememory_profile
Workflow
- Identify audience and desired tone.
- Preserve factual content and commitments.
- Remove generic phrasing, filler, and over-explanation.
- Add concrete transitions and natural rhythm.
- Offer variants when tone is ambiguous.
- Save approval-safe rewrite drafts with
writing_draft_createwhen the user wants a durable artifact. - Check final text against constraints.
Native Implementation Boundaries
- Use Stram writing draft tools, writing skills, and memory only.
- Do not import external reference humanizer scripts.
- Do not imitate a specific person without user-provided style context and permission.
Safety And Approval
- Do not change meaning.
- Do not add false emotional claims.
- External-visible messages still require approval before sending.
Verification
- Compare against must-keep facts.
- Confirm tone target.
- Label drafts as drafts.
Failure Modes
- Over-casualizing serious content.
- Removing important nuance.
- Adding unsupported warmth or certainty.
References
- Shortlist item:
humanized-writing.
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.
- 1mo ago First seen · 68 lines · 28 tokens per session scan A 2e0665a47aa7
humanized-writing is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 389 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…