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/bitwise-media-group/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/bitwise-media-group/skills/actions)<a href="https://agentmods.dev/plugins/bitwise-media-group/skills/actions"><img src="https://agentmods.dev/badge/plugins/bitwise-media-group/skills/actions/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/bitwise-media-group/skills/actions"><img src="https://agentmods.dev/badge/plugins/bitwise-media-group/skills/actions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
actions 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": "actions",
"version": "1.0.0",
"description": "GitHub Actions skills — least-privilege workflow style with truthy/falsey expressions, security hardening (SHA-pinning, no pull_request_target), wiring the bitwise reusable-workflow library, and an actionlint/zizmor validation loop.",
"author": {
"name": "Bitwise Media Group",
"email": "[email protected]"
},
"license": "MIT",
"keywords": ["github-actions", "ci", "workflows", "security", "actionlint", "zizmor"]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 529 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 4ef809268765
actions is a plugin published in the GitHub repository bitwise-media-group/skills (3 stars, last pushed today), 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
gha-dev
Skills and rules for creating GitHub Actions for the Marketplace.
data-analysis-ml-agent-skills
Evidence-first AI agent skills for reliable data analysis, machine learning, and reproducible model validation.
motherduck-skills
MotherDuck skills for agents and developers: use the CLI and Guides, explore schemas, write DuckDB SQL, build Dives and Flights, and ship analytics apps and pipelines.
motherduck-skills
MotherDuck skills for agents and developers: use the CLI and Guides, explore schemas, write DuckDB SQL, build Dives and Flights, and ship analytics apps and pipelines.
motherduck-skills
MotherDuck skills for Gemini CLI: use the MotherDuck CLI and Guides, explore live schemas, write DuckDB SQL, build Dives and Flights, and ship analytics apps and pipelines.
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…