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.
/plugin marketplace add YPares/agent-skillsnpx agentmods add plugins/ypares/agent-skills/nushell-skillsgit clone --depth 1 https://github.com/YPares/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/plugins/ypares/agent-skills/nushell-skills)<a href="https://agentmods.dev/plugins/ypares/agent-skills/nushell-skills"><img src="https://agentmods.dev/badge/plugins/ypares/agent-skills/nushell-skills.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
nushell-skills 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 yesterday.
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": "nushell-skills",
"description": "Skills for Nushell development, including plugin creation in Rust",
"source": "./",
"version": "1.0.0",
"homepage": "https://github.com/YPares/agent-skills",
"license": "MIT",
"keywords": [
"nushell",
"nu",
"plugin",
"rust",
"shell"
],
"strict": false,
"skills": [
"./nushell-usage",
"./nushell-plugin-builder"
]
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 123 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#nushell-skills 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.
- yesterday First seen · 20 lines scan A 4d751fe9e4ef
nushell-skills is a plugin published in the GitHub repository YPares/agent-skills (30 stars, last pushed 6d 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-09-03.
Other plugins, from other repositories
rust-learner
Learn Rust language features and crate updates using Actionbook + agent-browser.
t-tools
DDD-driven development skills, sub-agents and workflow commands for Rust, React, miniapp, and Flutter projects.
rust
Rust development tools for Claude Code.
xcode-build-skills
A multi-skill plugin for benchmarking and optimizing Xcode builds, compile hotspots, project settings, and Swift Package Manager dependency overhead.
migrate-tool
Generate database migrations and code migration scripts for framework upgrades.
skillctx
Make your agent skills portable by extracting hardcoded values into a central config and embedding resolver scripts.