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/curiositech/some_claude_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/curiositech/some_claude_skills/feature-manifest)<a href="https://agentmods.dev/plugins/curiositech/some_claude_skills/feature-manifest"><img src="https://agentmods.dev/badge/plugins/curiositech/some_claude_skills/feature-manifest.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
feature-manifest 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.
What it actually says
{
"name": "feature-manifest",
"description": "Manage feature manifests for code traceability \u2014 create features, validate manifest health, map features to code, update changelogs. Activates for 'feature manifest', 'feature tracking', 'code traceability'. NOT for project management, issue tracking, or git workflow."
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 57 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.
- today First seen · 5 lines scan A ca59cba9d4d2
feature-manifest is a plugin published in the GitHub repository curiositech/some_claude_skills (211 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-09-06.
Other plugins, from other repositories
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
rapido-direction
Chef de cabinet du dirigeant : Gmail, Google Calendar et Google Drive (compte connecté de chacun) unifiés avec CRM, FoodEatUp et n8n — journée du dirigeant, tri de boîte mail en brouillons, secrétariat commercial, coffre documents, délégation du récurrent.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills-only: owns folder layout and templates; runs the Obsidian CLI directly via the official obsidian-cli skill.
tgc-skills
A shipping pipeline for Claude Code: orchestrate a locked plan with fresh-context agents, polish the diff, ship it to a reviewed PR, run an agent review-fix loop until clean, and clean up after merge.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.