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.
git clone --depth 1 https://github.com/nibzard/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/plugins/nibzard/skills/tmux)<a href="https://agentmods.dev/plugins/nibzard/skills/tmux"><img src="https://agentmods.dev/badge/plugins/nibzard/skills/tmux/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/plugins/nibzard/skills/tmux"><img src="https://agentmods.dev/badge/plugins/nibzard/skills/tmux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tmux 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
{
"name": "tmux",
"version": "1.0.0",
"description": "Use tmux to run and test interactive CLI/TUI applications end-to-end. Includes utilities to start sessions, send keys, capture output, and cleanly stop processes.",
"homepage": "https://nibzard.com/skills/tmux",
"license": "MIT",
"author": {
"name": "nibzard",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 40 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 12 lines scan A 709f73cc821c
tmux is a plugin published in the GitHub repository nibzard/skills (2 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
anycap
Multimodal capabilities for AI agents through the AnyCap CLI.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
a11y-audit
Full accessibility audit with WCAG compliance checking.
skillgate
Deterministic finish-line gates for AI coding agents — define done once in .skillgate/done.yaml, then block commit, push and publish until it passes. Wires a fail-closed PreToolUse hook, evaluates agent patches in a network-off clone, and keeps CLAUDE.md/AGENTS.md from drifting apart.
manage-skills
Hardlink-based skill sharing across projects — one source of truth per skill, hardlinks everywhere else. Puts the manage-skills CLI on PATH and ships its own skills.
casely
Virtual QA lead: turns requirements into TestRail-ready test cases in one conversation, plus a runnable Postman collection when the spec describes an API.