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 JansenAnalytics/claudex --skill project-indexgit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/project-index)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/project-index"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/project-index.svg" alt="Measured on agentmods" 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.00018 | $0.00797 |
| Opus 5 | $0.00009 | $0.00398 |
| Sonnet 5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
project-index 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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-index
Kite's project registry — a structured JSON index of all active projects. Always know what's running, what state it's in, and what comes next.
Data file
${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/../index.json (default: ~/projects/index.json) — shared across all projects, one source of truth.
CLI location
${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs
Alias: alias pj="node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs"
When to use
Use this skill whenever the user (or Kite internally) asks about:
- "what are you working on?"
- "show project status"
- "what's the status of X?"
- "update the project index"
- "mark X as done"
- "what's next for Y?"
Commands
# List all projects
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs list
# Filter by status
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs list --status active
# Show full detail
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs show web-monitor
# Add a new project
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs add \
--id my-tool \
--name "My Tool" \
--path ~/projects/<your-tool> \
--github JansenAnalytics/my-tool \
--desc "Does something cool" \
--tags monitoring,cron \
--cron "*/15 * * * *"
# Update a project
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs update web-monitor \
--status active \
--last-action "Fixed regex check" \
--next "Add Slack notification"
# Append a note (timestamped)
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs note web-monitor "Added BTC price check"
# Mark done / archive
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs done stock-watcher
node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs archive stock-watcher
Kite behaviour
When the user asks about project status, Kite should:
- Run
listand present a clean summary - On
show <id>, present all fields - After completing any task that modifies a project, run
updateornoteto record it - When starting a new project, run
addimmediately
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.
- 4d ago First seen · 105 lines · 18 tokens per session scan A 9c0207c1dfe6
project-index is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 797 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-09-03.
Other skills, from other repositories
project-ops
Use when an operator wants to run a small or mid-sized project from a flat file instead of standing up Jira or Asana — dated milestones each with one named owner and a binary done-test, rule-driven RAG status, a RAID log, slippage detection, and a two-minute weekly status report. NOT sequencing the engineering work…
workflow-extract
Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine…
scheduler
Manage scheduled jobs — create, update, list, run remote agents on cron. Use when setting up recurring tasks, checking job status, or managing automation.
Scheduling work
Put work on the user's schedule, and read, amend or stop what is already there, using the scheduler tools.
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".