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 eveld/claude --skill determine-feature-sluggit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/determine-feature-slug)<a href="https://agentmods.dev/skills/eveld/claude/determine-feature-slug"><img src="https://agentmods.dev/badge/skills/eveld/claude/determine-feature-slug/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/eveld/claude/determine-feature-slug"><img src="https://agentmods.dev/badge/skills/eveld/claude/determine-feature-slug.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.00023 | $0.00823 |
| Opus 5 | $0.00012 | $0.00411 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
determine-feature-slug 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Determine Feature Slug
Interactively determine the next feature slug for personal workspace in the thoughts directory structure.
How It Works
-
Determine Namespace:
- Default to git user:
git config user.name | tr '[:upper:]' '[:lower:]' | tr ' ' '-' - Or accept namespace parameter
- Personal workspace:
thoughts/{namespace}/ - Shared workspace:
thoughts/shared/(used by share-docs skill)
- Default to git user:
-
Find Next Number:
- Scan
thoughts/{namespace}/directory for existing feature directories - Pattern:
^[0-9]{4}-.* - Find highest number and add 1
- Default to 0001 if no features exist
- Scan
-
Suggest Description:
- From research question: Extract key terms, convert to kebab-case
- From plan title: Extract feature name, convert to kebab-case
- Fallback: Prompt without suggestion
-
Prompt User with AskUserQuestion:
- Show suggested slug as an option
- User can accept suggestion or select "Other" to provide custom description
- Example:
AskUserQuestion: question: "Choose feature slug description (will be: erik/0004-[description])" header: "Feature Name" options: - "authentication-system" - Suggested based on context - Validate: Only lowercase letters, numbers, hyphens
-
Return Result:
- Format:
{namespace}/NNNN-description - Create directory:
thoughts/{namespace}/NNNN-description/
- Format:
Example Usage
# Determine namespace (default to git user)
NAMESPACE=$(git config user.name | tr '[:upper:]' '[:lower:]' | tr ' ' '-')
# Auto-detect next number in personal namespace
NEXT_NUM=$(ls -1 thoughts/${NAMESPACE}/ 2>/dev/null | grep -E '^[0-9]{4}-' | sort -r | head -1 | cut -d'-' -f1)
NEXT_NUM=$(printf "%04d" $((10#${NEXT_NUM:-0} + 1)))
# Suggest from context (research question, plan title)
SUGGESTED_DESC=$(echo "$RESEARCH_QUESTION" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-\|-$//g')
# Prompt user with AskUserQuestion
# Present suggested slug as option, user can select "Other" for custom input
# AskUserQuestion returns the selected value
DESC="$SUGGESTED_DESC" # Use result from AskUserQuestion
# Create directory in personal namespace
mkdir -p "thoughts/${NAMESPACE}/${NEXT_NUM}-${DESC}"
echo "${NAMESPACE}/${NEXT_NUM}-${DESC}"
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 · 90 lines · 23 tokens per session scan A a07e0f06ac82
determine-feature-slug is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 823 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-31.
Other skills, from other repositories
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
customer-persona-builder
Data-driven customer persona development combining market research, user behavior analysis, and segmentation frameworks. Use when creating buyer personas, ideal customer profiles (ICPs), or user archetypes.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.