feature-manifest

feature-manifest is a skill for Claude Code from curiositech/some_claude_skills. It costs 57 tokens per session (1,003 once invoked), scanned A, original, MIT.

A feature-manifest manager that records which files, tests, dependencies, and changes belong to each product feature. It also checks whether those records are accurate and up to date.

In plain words
What is it for?
Use it to create and update feature manifests, find the feature responsible for a file, validate manifests, check feature health, and update changelogs.
Why use it?
It makes the link between a feature and its implementation easier to trace, reducing stale records, orphaned files, and unclear ownership.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the feature-manifest plugin — 1 skill shipped together

Good fit Use it to create and update feature manifests, find the feature responsible for a file, validate manifests, check feature health, and update changelogs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/curiositech/some_claude_skills/feature-manifest
Install

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.

Any agent
npx skills add curiositech/some_claude_skills --skill feature-manifest
Clone the repo
git clone --depth 1 https://github.com/curiositech/some_claude_skills

Made for: Claude Code.

Or install feature-manifest, the plugin that ships this one along with the rest of its 1 skill.

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 feature-manifest

README.md
[![agentmods](https://agentmods.dev/badge/skills/curiositech/some_claude_skills/feature-manifest/github.svg)](https://agentmods.dev/skills/curiositech/some_claude_skills/feature-manifest)
Your own site
<a href="https://agentmods.dev/skills/curiositech/some_claude_skills/feature-manifest"><img src="https://agentmods.dev/badge/skills/curiositech/some_claude_skills/feature-manifest/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.

agentmods 80×15 button for feature-manifest

Your own site · 80×15
<a href="https://agentmods.dev/skills/curiositech/some_claude_skills/feature-manifest"><img src="https://agentmods.dev/badge/skills/curiositech/some_claude_skills/feature-manifest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,003 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00057 $0.01003
Opus 5 $0.00028 $0.00502
Sonnet 5 $0.00011 $0.00201
Haiku 4.5 $0.00006 $0.00100

Measured 7d ago against content hash 848e5ffa66d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

feature-manifest 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.

.claude/skills/feature-manifest/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature Manifest Management

This skill helps you work with the feature manifest system that tracks the relationship between features and their implementations.

When to Use This Skill

  • Creating a new feature
  • Modifying existing feature code
  • Checking which feature owns a file
  • Validating manifest accuracy
  • Updating changelogs
  • Running feature health checks

Quick Commands

# List all features
npm run feature:info -- --list

# Get details about a feature
npm run feature:info -- <feature-id>

# Find which feature owns a file
npm run feature:info -- --files <filepath>

# Validate all manifests
npm run feature:validate

# Check feature health (staleness, orphans, coverage)
npm run feature:health

# Create a new feature manifest
npm run feature:create

Workflow: Creating a New Feature

  1. Create the manifest first:

    npm run feature:create -- --id=my-feature --name="My Feature"
    
  2. Implement the feature, adding files as you go

  3. Update the manifest with:

    • All implementation files in implementation.files
    • Tests in tests.unit/integration/e2e
    • Dependencies in dependencies.internal/external
    • Environment variables in dependencies.env_vars
  4. Validate before committing:

    npm run feature:validate
    

Workflow: Modifying an Existing Feature

  1. Read the manifest first:

    npm run feature:info -- &lt;feature-id>
    
  2. Make your changes to the implementation files

  3. Update the manifest:

    • Add new files to implementation.files
    • Update history.last_modified to today's date
    • Add a changelog entry
  4. Validate:

    npm run feature:validate
    

Manifest Structure

id: feature-id
name: Human Readable Name
status: complete  # planned | in-progress | complete | deprecated
priority: P1

description: |
  What this feature does and why it exists.

implementation:
  files:
    - src/app/api/feature/route.ts
    - src/lib/feature.ts
  entry_point: src/lib/feature.ts
  database_tables:
    - tableName
  api_routes:
    - POST /api/feature

tests:
  unit:
    - src/lib/__tests__/feature.test.ts
  integration: []
  e2e: []

dependencies:
  internal:
    - features/authentication.yaml
  external:
    - package-name
  env_vars:
    - FEATURE_SECRET
  secrets:
    - feature-api-key

history:
  created: "2024-12-01"
  last_modified: "2024-12-23"

changelog:
  - version: "1.0.0"
    date: "2024-12-23"
    changes:
      - "Initial implementation"

Read the full file on GitHub · 160 lines

Files

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.

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. 7d ago First seen · 160 lines · 57 tokens per session scan A 848e5ffa66d6

Subscribe to this mod's changes

feature-manifest is a skill published in the GitHub repository curiositech/some_claude_skills (219 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 1,003 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens