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 ZekaiSuni/claude-for-legal-turkish --skill skill-managergit clone --depth 1 https://github.com/ZekaiSuni/claude-for-legal-turkishWrote 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/zekaisuni/claude-for-legal-turkish/skill-manager)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/skill-manager"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/skill-manager/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/zekaisuni/claude-for-legal-turkish/skill-manager"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/skill-manager.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.00066 | $0.01075 |
| Opus 5 | $0.00033 | $0.00537 |
| Sonnet 5 | $0.00013 | $0.00215 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
skill-manager 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Manager
Purpose
Remove or quiet a community skill after install. Symmetric with the installer:
the installer writes files with user approval, the skill-manager removes or
disables them with user approval. The installer's audit trail (install-log.yaml)
is the source of truth for what this skill may act on.
What this skill may act on
Only community skills installed through this hub. Identification rule:
- The skill's name must appear in
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yamlwith a most-recent action ofinstallorenable(notuninstall). - The skill's files must resolve to a path outside the built-in plugin directories that ship with claude-for-legal.
If either check fails, refuse and tell the user why. Never delete or rename files inside a first-party plugin.
Built-in plugins (do not touch)
The 12 core plugins that ship with claude-for-legal are off-limits from this
command. The canonical list lives in the hub's CLAUDE.md under "Built-in
plugins." Examples include commercial-legal, corporate-legal,
employment-legal, privacy-legal, product-legal, regulatory-legal,
ai-governance-legal, litigation-legal, litigation-legal,
law-student, legal-clinic, and the hub itself (legal-builder-hub). If
the caller names a skill that resolves into any of these, refuse.
Workflow — uninstall
Step 1: Verify the skill is community-installed
Read install-log.yaml. Find the most recent entry for the named skill.
If not found or if the last action is uninstall: say so and stop.
Step 2: Resolve files
Determine the install path from the log (written at install time).
Enumerate every file and subdirectory. Also identify any config the skill
wrote to the user's ~/.claude/plugins/config/... — surface this to the user
but do not delete it by default (configuration may be worth keeping for a
later re-install).
Step 3: Show and confirm
Display:
- The skill's install directory path
- Every file that will be deleted
- Any config directories that will NOT be deleted (with a note that the user can delete them manually if desired)
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.
- 9d ago First seen · 133 lines · 66 tokens per session scan A 5f225dc69a29
skill-manager is a skill published in the GitHub repository ZekaiSuni/claude-for-legal-turkish (103 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,075 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…