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 jeremymcs/skills --skill new-featuregit clone --depth 1 https://github.com/jeremymcs/skillsWrote 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/jeremymcs/skills/new-feature)<a href="https://agentmods.dev/skills/jeremymcs/skills/new-feature"><img src="https://agentmods.dev/badge/skills/jeremymcs/skills/new-feature/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/jeremymcs/skills/new-feature"><img src="https://agentmods.dev/badge/skills/jeremymcs/skills/new-feature.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.00062 | $0.00568 |
| Opus 5.5 | $0.00025 | $0.00227 |
| Sonnet 5.5 | $0.00012 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
new-feature 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 2mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Feature
Use this skill when the user wants recommended new or next features for the current project.
The output should be actionable recommendations, not a broad product essay.
Workflow
- Establish the project shape.
- Read
README,AGENTS.md,CONTRIBUTING,DESIGN, roadmap docs, ADRs, and package manifests if present. - Inspect source layout, app routes, tests, examples, scripts, and recent commits.
- Review open issues or PRs when the project issue tracker is available.
- Read
- Identify signals.
- Existing product capabilities and obvious gaps.
- Repeated TODOs, FIXME comments, failing/skipped tests, missing docs, missing workflows, or incomplete UX paths.
- Recent work that suggests a natural next step.
- Operational needs such as setup, observability, testing, security, accessibility, or release automation.
- Generate candidate features.
- Prefer features that are small enough to start soon and meaningful enough to demo.
- Avoid speculative features that are not supported by project evidence.
- Do not recommend dependency churn as a feature unless it unlocks user-visible value.
- Rank recommendations.
- Default ranking factors: user value, evidence strength, effort, risk, and fit with the project direction.
- Mark uncertainty explicitly when the repo lacks product context.
- Present the result.
- Lead with the top 3-5 recommendations.
- For each recommendation include:
- Feature name
- Why now
- Evidence from the project
- Suggested first slice
- Effort and risk
- End with a short "Not recommended yet" section when there are tempting but premature ideas.
Output Format
## Recommended Next Features
### 1. Feature name
Why now:
Evidence:
Suggested first slice:
Effort/risk:
### 2. Feature name
...
## Not Recommended Yet
- Idea: reason to defer.
Guardrails
- Cite concrete repo signals, file paths, issue references, or observed behavior.
- If using external research, say what was checked and link sources.
- Do not invent users, roadmap commitments, metrics, or business priorities.
- Ask one targeted question only if the project has too little context to rank recommendations responsibly.
- Do not create issues or PRs unless the user explicitly asks.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 73 lines · 62 tokens per session scan A c2ac4e3e07e9
new-feature is a skill published in the GitHub repository jeremymcs/skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 568 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…