Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add joey-barbier/ClaudeCode-Plugin/plugin install horka-project-indexWrote 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/joey-barbier/claudecode-plugin/horka-project-index)<a href="https://agentmods.dev/skills/joey-barbier/claudecode-plugin/horka-project-index"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-project-index/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/joey-barbier/claudecode-plugin/horka-project-index"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-project-index.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.00159 | $0.02064 |
| Opus 5 | $0.00079 | $0.01032 |
| Sonnet 5 | $0.00032 | $0.00413 |
| Haiku 4.5 | $0.00016 | $0.00206 |
Grade A, and why
horka-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 11d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Index
Global project registry for Claude Code's multi-project view (Agent View /
"FleetView"). Claude identifies a project by its cwd, but has no native way to
name/describe a project, nor to tie a generic command ("write the changelog") to
the right folder. This skill fills that gap.
Scope: multi-project by design, but stays quiet if you only have one project
(nothing to disambiguate → act on the current project). Requires Python ≥ 3.7 and
git on PATH (macOS / Linux / WSL / Windows). Honors CLAUDE_CONFIG_DIR.
Files
Let $SKILL be this skill's own directory — its absolute path is given at
skill-load time as "Base directory for this skill: …", and equals
${CLAUDE_PLUGIN_ROOT}/skills/horka-project-index when installed as a plugin. Always
call the script with that absolute path; never assume a hardcoded location.
- Builder:
$SKILL/build_index.py(no hardcoded user paths) - Canonical index:
<config>/projects-index.json - Readable view:
<config>/PROJECTS.md
<config> = $CLAUDE_CONFIG_DIR else ~/.claude. Use --status for the exact paths.
Data model
Two entry types:
project— a folder actually opened with Claude (source: the realcwdread from the transcripts<config>/projects/*/*.jsonl; folder names are never decoded — ambiguous:dev-cc≠dev/cc).workspace— a parent folder containing a.claude/and ancestor of at least one project (e.g. a monorepoLibTracker/hosting API + front + sdk). It may have no history but can own shared skills/commands — that is often the level that should run a cross-cutting action.
Each entry carries: name, path, type, exists, aliases, stack,
description, skills, commands (what the folder provides via its
.claude/), git_remote, branch, last_active, and members (workspaces).
§A — Resolve a command's target
Goal: go from a fuzzy command to the right folder, never by guessing.
Golden rule: nominal first, and when in doubt → ask (AskUserQuestion).
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.
- 11d ago First seen · 167 lines · 159 tokens per session scan A cdede3ee8083
horka-project-index is a skill published in the GitHub repository joey-barbier/ClaudeCode-Plugin (22 stars, last pushed 2mo ago), licensed MIT. It adds 159 tokens to every session and 2,064 once invoked, about $0.0008 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
remove
Remove a deployed framework or addon from the current workspace.