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 swan-gtm/gtm-skills --skill kill-the-wall-of-textgit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/kill-the-wall-of-text)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/kill-the-wall-of-text"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/kill-the-wall-of-text/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/swan-gtm/gtm-skills/kill-the-wall-of-text"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/kill-the-wall-of-text.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.00162 | $0.01537 |
| Opus 5.5 | $0.00065 | $0.00615 |
| Sonnet 5.5 | $0.00032 | $0.00307 |
| Haiku 4.5 | $0.00016 | $0.00154 |
Grade A, and why
kill-the-wall-of-text 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applies each time raw work must go to a person who did not make it. Produces one interactive page that the recipient can review in seconds, and that the sender has read and signed.
The rule: work like a lawyer who talks to a five-year-old. The lawyer signs each word and stands behind it. Nobody gives a five-year-old ten pages of text; someone shows the story.
The measure: work is slop if the review takes longer than the generation. This play inverts that ratio. The build takes longer, so that the review takes seconds.
The three layers
Each page has all three.
- Top, 10 seconds. The verdict in one sentence. The ask: what the recipient must do, and by when. A maximum of three key numbers.
- Body, 2 minutes. An interactive view in the shape that fits the content.
- Evidence, on demand. Sources, method, assumptions, and the content that was cut. Folded. Nothing is lost, and nothing is in the way.
Test for the top: if the recipient reads only the top and closes the page, do they know the answer and their next action?
The play
- Read all of the raw work. Extract the recipient, the ask, the verdict, each fact with its location in the source, and the gaps: missing data, contradictions, claims with no evidence.
- Ask a maximum of two questions, in one message. "Who gets this, and what must they do with it?" and "What is the one thing they must understand?" Offer a proposed verdict, so that the human can say yes. Do not ask what the context answers. A skipped question becomes a labeled assumption, not a second question.
- Select the shape. A report becomes a dashboard. A plan becomes a one-page view. A decision becomes an option comparison. A code change becomes a diagram of what moved. Read
references/shape-table.mdfor the ten shapes and the rule for two shapes that fit. - Write each visible word in Simplified Technical English. Short active sentences, one word for one thing, no idioms, absolute dates, one named owner for each action. Read
references/writing-rules.mdbefore you write; it also has the fidelity rules and the cases where the two sets of rules meet. - Publish the first version quickly. Start from
references/page-skeleton.md. The first version shows a "Draft, not signed" banner. Chat gets one line: "This is V1. Tell me what goes on top, what to cut, and what is wrong." - Check before each publish. Read
references/pre-publish-check.md. It has a script that finds sentences that break the writing rules, calculates the read time, and lists each number that is not in the source. - Run the review loop. The human decides what goes on top, what to cut, and what is wrong. Each block has Keep, Cut, Fix, and Move up controls, and one button copies the feedback as text for the chat. Apply the feedback to the current page; do not build it again. Read
references/review-loop-and-signing.md. - Get the signature. When the human approves, ask one time: "Did you read all of it, and do you stand behind it?" On yes, the banner changes to "Signed by NAME, DATE". No signature, no change.
What ships with it
6 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 · 69 lines · 162 tokens per session scan A eaee1405d6a1
kill-the-wall-of-text is a skill published in the GitHub repository swan-gtm/gtm-skills (181 stars, last pushed 2d ago), licensed MIT. It adds 162 tokens to every session and 1,537 once invoked, about $0.0006 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-10-12.
Other skills, from other repositories
team-motivation-ops
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict…
covey-seven-habits
Applies Stephen Covey's Seven Habits framework for personal and interpersonal effectiveness, progressing from dependence through independence to interdependence. Covers proactivity, mission clarity, prioritization, Win/Win thinking, empathic listening, synergy, and renewal. Use when conducting personal effectiveness…
decision-making-under-pressure
Provides practical habits for making better decisions faster -- reframing problems before solving them, knowing when to stop deliberating, balancing intuition with analysis, resisting 'just this once' compromises, and breaking overthinking cycles. Use when facing a high-stakes choice with incomplete data, sensing that…
delegation-and-empowerment
Develops the daily practice of effective delegation, accountability diagnosis, and team empowerment. Covers assessing which tasks require personal attention, clarifying scope and context for delegated work, allowing productive struggle, recognising and correcting micromanagement, and leading through influence rather…
focus-and-priority-management
Delivers daily scheduling habits, meeting hygiene, attention management, and boundary-setting techniques for leaders whose calendars have become their strategy by default. Use when urgent tasks crowd out important ones, when meeting load exceeds productive work time, when a leader cannot recall their last hour of…
introvert-leadership
Reframes introversion as a leadership asset and provides practical strategies for introverted leaders -- managing energy, deploying extroversion selectively, scheduling around social depletion, protecting reflection time, and supporting extroverted team members. Use when an introverted leader feels pressure to perform…