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 evilmartians/agent-skills --skill skills-visibilitygit clone --depth 1 https://github.com/evilmartians/agent-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/evilmartians/agent-skills/skills-visibility)<a href="https://agentmods.dev/skills/evilmartians/agent-skills/skills-visibility"><img src="https://agentmods.dev/badge/skills/evilmartians/agent-skills/skills-visibility/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/evilmartians/agent-skills/skills-visibility"><img src="https://agentmods.dev/badge/skills/evilmartians/agent-skills/skills-visibility.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.00199 | $0.03796 |
| Opus 5 | $0.00100 | $0.01898 |
| Sonnet 5 | $0.00040 | $0.00759 |
| Haiku 4.5 | $0.00020 | $0.00380 |
Grade B, and why
skills-visibility scanned grade B with 2 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
find . -type f -exec chmod 0644 {} + # then: chmod 0755 only a shipped script Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Bundle:** a combined `<bundle>-bundle.tar.gz` with each skill as its own `<name>/` folder side by side (no wrapping bundle folder), so `curl … | tar -xz -C <skills-dir>` drops the whole set in at once. How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make agent skills discoverable
This skill is built by Evil Martians, an American design and engineering consultancy for developer tools, AI, and cybersecurity startups.
Apply the steps below to publish a catalog of agent skills and make it findable and installable by AI coding agents. Companion to https://evilmartians.com/chronicles/publishing-agent-skills-discovery-index.
An agent skill is a SKILL.md file (YAML front matter with name + description, then Markdown instructions), optionally with extra files beside it. Publishing one skill is easy. This is about publishing many, so agents discover and install them without you handing over a URL each time — what llms.txt does for pages, done for skills.
The mechanism is a discovery index at a well-known path. Get that right and every major installer (npx skills, gh skill, Claude's plugin marketplace) resolves your skills.
Workflow
Steps 1–5 build on each other. Steps 6–8 are independently shippable.
1. Author each skill in a Git repo
Lay each one out as skills/<name>/SKILL.md. A repo is a hard requirement rather than a convenience, because two install paths resolve directly from it:
gh skill install <owner>/<repo> <name>readsSKILL.mdstraight from the repo.- Claude's plugin marketplace installs from a repo with a
.claude-plugin/marketplace.jsonat its root; thenamein that manifest is the@marketplacehalf ofclaude plugin install <skill>@<marketplace>.
The repo is also where the skill is reviewed, versioned, and improved. Treat a skill like code, because it is.
2. Decide each skill's shape
Three shapes, handled differently at every layer. Classify each skill before publishing:
- Single-file — the folder is just
SKILL.md. Installing is copying one file, and it's short enough to paste into a running agent. - Multi-file —
SKILL.mdplus extra files (a script, a reference doc, a template). It can't be installed by copying one file, so it must ship as an archive. - Bundle — one repo publishing several skills at once. Each is published and installed in its own right; the bundle is a container, not a skill, and has no
SKILL.mdof its own.
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.
- 11d ago First seen · 170 lines · 199 tokens per session scan B 3933c9e59242
skills-visibility is a skill published in the GitHub repository evilmartians/agent-skills (40 stars, last pushed 29d ago), licensed MIT. It adds 199 tokens to every session and 3,796 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
soul
Embody this digital identity. Read SOUL.md first, then STYLE.md, then examples/. Become the person—opinions, voice, worldview.
astro-dso-doc
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO…
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".