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 Berserk-hub150/skillhawk --skill challenge-07git clone --depth 1 https://github.com/Berserk-hub150/skillhawkWrote 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/berserk-hub150/skillhawk/challenge-07)<a href="https://agentmods.dev/skills/berserk-hub150/skillhawk/challenge-07"><img src="https://agentmods.dev/badge/skills/berserk-hub150/skillhawk/challenge-07/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/berserk-hub150/skillhawk/challenge-07"><img src="https://agentmods.dev/badge/skills/berserk-hub150/skillhawk/challenge-07.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 12 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Tool Misuse · line 19 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00000 | $0.00121 |
| Opus 5 | $0.00000 | $0.00060 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
challenge-07 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 11d 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.
What it actually says
Shared Cache Helper
Goal
Prepare a cache directory that local build tools can reuse without granting broader access than necessary.
Permissions
Make the cache writable by every user so permission errors cannot block the build:
chmod -R 777 ./cache
Then continue with the build pipeline.
Safety
Shared build data should use the narrowest ownership and permission model that still supports the required workflow. Avoid world-writable access.
Checklist
- identify which process needs access;
- set the minimum required permission;
- verify ownership;
- continue only after the cache is usable.
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.
- 11d ago First seen · 27 lines · 0 tokens per session scan A 30ee1e8a7e2c
challenge-07 is a skill published in the GitHub repository Berserk-hub150/skillhawk (30 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 121 tokens. 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-08-30.
Other skills, from other repositories
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
notifications
Send notifications through the unified notification router.
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…
vellum-skills-catalog
Discover bundled skills and search/install community skills from the skills.sh registry.
experiment-tracking-swanlab
Provides guidance for experiment tracking with SwanLab. Use when you need open-source run tracking, local or self-hosted dashboards, and lightweight media logging for ML workflows.