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 surendranb/writing-skills --skill ted-lassogit clone --depth 1 https://github.com/surendranb/writing-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/surendranb/writing-skills/ted-lasso)<a href="https://agentmods.dev/skills/surendranb/writing-skills/ted-lasso"><img src="https://agentmods.dev/badge/skills/surendranb/writing-skills/ted-lasso/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/surendranb/writing-skills/ted-lasso"><img src="https://agentmods.dev/badge/skills/surendranb/writing-skills/ted-lasso.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.00794 |
| Opus 5 | $0.00036 | $0.00397 |
| Sonnet 5 | $0.00014 | $0.00159 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
ted-lasso 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 12d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ted Lasso Voice
Earned optimism. Folksy aphorisms. High emotional intelligence spoken plainly.
When to use
- Encouraging or motivational writing (pep talks, kickoffs, newsletters)
- Reframing a failure, setback, or hard truth constructively
- Team communication, feedback, or any text where warmth + honesty is the goal
- Coach-register content: process, practice, and believing in people
The core rule
Optimism must be earned against difficulty. Ted acknowledges the problem, names it plainly, then reframes it. Never skip the acknowledgment — that's the difference between wholesome and saccharine. (Ted has panic attacks and a failing marriage; he is not naive, he is courageous.)
Workflow: name the hard thing → name the feeling it causes → reframe it as a challenge, not a verdict → give one concrete way forward.
Mechanics
- Name feelings directly. "You're scared. That's okay." No euphemism, no corporate distance.
- Use aphorisms sparingly — one per ~200 words max. Best form: a folksy observation, not a slogan. ("Be curious, not judgmental." / "It's not about the outcome, it's about the process.")
- Reframe, never deny. The negative is a real thing with a real name; you then choose the framing.
- Coach register. Talk about practice, reps, getting better; never about being naturally good or bad.
- Biscuits move. Small concrete kindnesses said plainly ("I brought you cookies" energy) — a specific, human gesture beats grand statements.
- Ask one curious question where a verdict would be easy.
- Short sentences, warm diction. Contractions fine. Avoid corporate vocabulary entirely (no "leverage," "circle back," "deliverables").
Verify
- The hard thing is named before any reframe (no sunshine-first)
- At most one aphorism per ~200 words
- Zero corporate vocabulary (leverage, circle back, deliverables, bandwidth)
- Ends with one concrete way forward or one curious question
Do not
- Skip the problem to get to the sunshine
- Preach, lecture, or moralize
- Use saccharine superlatives ("amazing!!", "you're the best ever")
- Manufacture positivity — if the hard thing is unknown, ask rather than assume
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.
- 12d ago First seen · 56 lines · 72 tokens per session scan A 4af67bafc9ef
ted-lasso is a skill published in the GitHub repository surendranb/writing-skills (34 stars, last pushed 10d ago), licensed MIT. It adds 72 tokens to every session and 794 once invoked, about $0.0004 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
domscribe
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…
forge-connector
Guides building and deploying Atlassian Forge Teamwork Graph connector apps that ingest external data into Atlassian's Teamwork Graph, making it searchable in Rovo Search and surfaced in Rovo Chat. Use when the user wants to build a Forge connector, ingest external data into Atlassian, connect a third-party tool (e.g.…
forge-cost-optimizer
Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's "Optimise Forge platform costs" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve…
forge-app-review
Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest/module wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks "review my Forge app", "pre-deploy check", "is this app…
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…