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/youdotcom-oss/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/mcp/youdotcom-oss/agent-skills/you)<a href="https://agentmods.dev/mcp/youdotcom-oss/agent-skills/you"><img src="https://agentmods.dev/badge/mcp/youdotcom-oss/agent-skills/you/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/mcp/youdotcom-oss/agent-skills/you"><img src="https://agentmods.dev/badge/mcp/youdotcom-oss/agent-skills/you.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
you 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- you — 86% identical, 5 lines differ
What it actually says
{
"you": {
"type": "http",
"url": "https://api.you.com/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- today First seen · 6 lines scan A 64896535b996
you is an MCP server published in the GitHub repository youdotcom-oss/agent-skills (69 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-12.
Other mcp servers, from other repositories
cargo
Structured Rust cargo operations (build, test, clippy) as typed JSON. Runs locally from the @paretools/cargo npm package.
docker
Structured Docker operations (ps, images, logs, build) as typed JSON. Runs locally from the @paretools/docker npm package.
http
MCP server for HTTP requests (curl) with structured, token-efficient output. Runs locally from the @paretools/http npm package.
lint
Structured linting output (ESLint, format-check) as typed JSON diagnostics. Runs locally from the @paretools/lint npm package.
make
MCP server for Make/Just task runners with structured, token-efficient output. Runs locally from the @paretools/make npm package.
pare-git
Pare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON. Runs locally from the @paretools/git npm package.