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 trtmn/agent-plugins --skill cowsaygit clone --depth 1 https://github.com/trtmn/agent-pluginsWrote 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/trtmn/agent-plugins/cowsay)<a href="https://agentmods.dev/skills/trtmn/agent-plugins/cowsay"><img src="https://agentmods.dev/badge/skills/trtmn/agent-plugins/cowsay/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/trtmn/agent-plugins/cowsay"><img src="https://agentmods.dev/badge/skills/trtmn/agent-plugins/cowsay.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.00034 | $0.00571 |
| Opus 5.5 | $0.00014 | $0.00228 |
| Sonnet 5.5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
cowsay 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
cowsay
Run the Python cowsay package to show an ASCII cow (or other character) saying the user's custom text.
When to use
- User asks for a cow to say something (e.g. "make a cow say hello", "cowsay hello world").
- User provides custom text they want displayed in cowsay style.
Instructions
- Get the text – Use the exact phrase or sentence the user wants the cow to say. If they didn’t specify, ask or use a short default (e.g. "Hello!").
- Run cowsay – Execute the script (uses
uvx cowsayso no install or local-dir conflict):bash /mnt/skills/user/cowsay/scripts/cowsay.sh "user's text here"- Escape or quote the text so spaces and special characters are preserved.
- Show the result – Present the command output to the user as the cow’s speech bubble.
Usage
bash /mnt/skills/user/cowsay/scripts/cowsay.sh "Your message here"
Requires uv (or run uvx cowsay "Your message here" directly).
Arguments:
- Message text – The line the cow should say (default: use the text the user provided or ask).
Examples:
bash /mnt/skills/user/cowsay/scripts/cowsay.sh "Hello, world!"bash /mnt/skills/user/cowsay/scripts/cowsay.sh "Ship it!"
Output
The tool prints an ASCII-art cow with the given text in a speech bubble. Example:
_____________
< Hello world! >
-------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
Present results to user
Show the cowsay output in a code block (e.g. preformatted text) so the cow art is aligned correctly.
Troubleshooting
uvx: command not found– Install uv, thenuvx cowsaywill work.- Broken layout – Use a fixed-width font when displaying the output.
- Special characters – Keep the message in quotes so the shell doesn’t split or interpret it.
What ships with it
1 file 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.
- 1mo ago First seen · 67 lines · 34 tokens per session scan A df31fa70a8ee
cowsay is a skill published in the GitHub repository trtmn/agent-plugins (2 stars, last pushed 11d ago), licensed Unlicense. It adds 34 tokens to every session and 571 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…