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 agentmods add skills/stacklok/toolhive-studio/skill-editornpx skills add stacklok/toolhive-studio --skill skill-editorgit clone --depth 1 https://github.com/stacklok/toolhive-studioWhat 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 | $0.00040 | $0.00445 |
| Opus 5 | $0.00020 | $0.00222 |
| Sonnet 5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade D, and why
skill-editor scanned grade D with 2 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 2d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -la .claude/skills/ Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .claude/skills/<name> .codex/skills/<name> .cursor/skills/<name> What it actually says
Skill Editor
Edit existing AI agent skills while keeping Claude, Codex, and Cursor in sync.
Workflow
- Always edit Claude first -
.claude/skills/<name>/SKILL.mdis the canonical source - Replicate with CLI - Copy changes to
.codex/skills/and.cursor/skills/ - Never edit Codex/Cursor directly - They are copies of Claude's version
Finding Existing Skills
List all skills:
ls -la .claude/skills/
Read a skill:
cat .claude/skills/<name>/SKILL.md
Editing a Skill
- Read the current skill content from
.claude/skills/<name>/SKILL.md - Make the requested changes
- Replicate to other agents:
cp .claude/skills/<name>/SKILL.md .codex/skills/<name>/ cp .claude/skills/<name>/SKILL.md .cursor/skills/<name>/
Verification
Always verify sync after editing:
diff .claude/skills/<name>/SKILL.md .codex/skills/<name>/SKILL.md
diff .claude/skills/<name>/SKILL.md .cursor/skills/<name>/SKILL.md
No output means files are identical.
Common Edits
- Update description - Improve auto-discovery keywords
- Add instructions - Expand the skill's capabilities
- Fix errors - Correct mistakes in the skill logic
- Add references - Create
references/directory for supporting docs
Deleting a Skill
Remove from all three locations:
rm -rf .claude/skills/<name> .codex/skills/<name> .cursor/skills/<name>
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.
- 2d ago First seen · 65 lines · 40 tokens per session scan D 7b1d17e048e4
skill-editor is a skill published in the GitHub repository stacklok/toolhive-studio (163 stars, last pushed 4d ago), licensed Apache-2.0. It adds 40 tokens to every session and 445 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 2 findings (enumerates other installed skills, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
investigate-issue
Investigate a GitHub issue by fetching details, analyzing the codebase, researching documentation, and presenting an actionable implementation plan with test guidance. Use when asked to investigate, analyze, triage, or plan work for a GitHub issue. Invoked with /investigate-issue or /investigate-issue (prompts for ID).
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
bugcrowd-reporting
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…
hunt-ato
Hunt account takeover taxonomy — 9 distinct paths to ATO, plus chains. Paths: (1) password reset flaws (host-header injection redirects token, predictable/numeric token, Referer leak, no-expiry/reuse), (2) email change without re-auth, (3) OAuth account-link CSRF, (4) MFA bypass (per hunt-mfa-bypass), (5) session…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…