HunterStick: Skill for Claude Code

.claude/skills/derive-properties/SKILL.md

derive-properties is a skill for Claude Code from tarekmo0/HunterStick. It costs 24 tokens per session (94 once invoked), scanned A, original, MIT.

A procedure for turning collected evidence into testable properties, meaning statements that can be checked against a system's behavior or exposed attack surface.

In plain words
What is it for?
It helps derive and organize properties for security testing or other focused system evaluation.
Why use it?
It helps convert observations into concrete checks instead of leaving them as untested notes.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code; mentions AGENTS.md.

This is tarekmo0/HunterStick's own configuration. It tells Claude Code how to work on HunterStick itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything HunterStick configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tarekmo0/HunterStick. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tarekmo0/HunterStick/main/.claude/skills/derive-properties/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/tarekmo0/HunterStick

Made for: Claude Code.

Wrote 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.

agentmods badge for derive-properties

README.md
[![agentmods](https://agentmods.dev/badge/skills/tarekmo0/hunterstick/derive-properties.svg)](https://agentmods.dev/skills/tarekmo0/hunterstick/derive-properties)
Your own site
<a href="https://agentmods.dev/skills/tarekmo0/hunterstick/derive-properties"><img src="https://agentmods.dev/badge/skills/tarekmo0/hunterstick/derive-properties.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 94 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00094
Opus 5 $0.00012 $0.00047
Sonnet 5 $0.00005 $0.00019
Haiku 4.5 $0.00002 $0.00009

Measured 6d ago against content hash 32ef6bf04f88, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

derive-properties 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 6d 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.

.claude/skills/derive-properties/SKILL.md · 11 lines

What it actually says

Read skills/context-and-prioritization/derive-properties.md and follow it.

That file is the single body for this skill; this pointer exists only so Claude Code can auto-trigger on the description above. Every other runtime dispatches to the same file through the router table in AGENTS.md.

Changes

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.

  1. 6d ago First seen · 11 lines · 24 tokens per session scan A 32ef6bf04f88

Subscribe to this mod's changes

derive-properties is a skill published in the GitHub repository tarekmo0/HunterStick (13 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 94 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens