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 event4u-app/agent-config --skill description-assistgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/description-assist)<a href="https://agentmods.dev/skills/event4u-app/agent-config/description-assist"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/description-assist/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/event4u-app/agent-config/description-assist"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/description-assist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.01863 |
| Opus 5 | $0.00022 | $0.00932 |
| Sonnet 5 | $0.00009 | $0.00373 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
description-assist 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 7d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description-assist
When to use
- The user says "make this description pushier", "this description is weak", "will this ever fire", "rewrite the description".
- Called from within the Draft phase of one of the writing skills
(
skill-writing,rule-writing,command-writing,guideline-writing). - Auditing a skill flagged by
audit_skill_descriptions.tsastoo-short,no-trigger-prefix, ordescription_too_longinskill_linter.ts.
Do NOT use this skill when:
- The user wants to change the body, name, or procedure — one field per turn.
- The content is not an agent artifact (READMEs, docs, commit messages).
- The user explicitly asked for a fresh description — write it, don't audit.
The contract
- No silent edits. Every proposed variant is a suggestion presented with numbered options; the user picks before anything is written.
- No Claude API grading loop. You reason from your context only. No separate AI pass evaluates your suggestions.
- Max two rounds. Propose → reject → refine → reject → stop. If the second round is rejected, ask one clarifying question and exit.
- One field per turn. Only
description. Trigger phrases, name, and body belong to their own turns.
Procedure
1. Read the current description
Open the target file. Read the description: value in full. If the value
is missing, abort and route to the relevant writing skill instead.
2. Inspect the description against four criteria
Normative source: skill-quality § Description Triggering.
| Check | Pass when… |
|---|---|
| Length | ≤ 200 characters (hard cap; linter errors description_too_long) |
| Trigger prefix | Starts with "Use when …" or equivalent trigger phrasing |
| Trigger classes | Names ≥ 2 of: domain, symptom, user phrasing, tool, file type |
| Undertrigger tail | Ends with "… even if the user doesn't say {name}" or equivalent |
Report which checks pass / fail in one compact line — not a long essay.
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.
- 7d ago First seen · 196 lines · 44 tokens per session scan A bb7416436982
description-assist is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,863 once invoked, about $0.0002 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
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.