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 lubluniky/dale --skill dale-indexgit clone --depth 1 https://github.com/lubluniky/daleWrote 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/lubluniky/dale/dale-index)<a href="https://agentmods.dev/skills/lubluniky/dale/dale-index"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-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/lubluniky/dale/dale-index"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-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.00051 | $0.00837 |
| Opus 5 | $0.00026 | $0.00418 |
| Sonnet 5 | $0.00010 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
dale-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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dale Index
Build a compact source of truth from the repository as it exists now. The calling agent integrates and writes; independent discovery uses read-only subagents where repository scope justifies parallel work.
Bound the refresh
Inspect applicable instructions, Git state, manifests, entrypoints, tests, schemas, and existing primitives. Preserve unrelated edits and hand-written content unless current evidence disproves it. No saved Codex project is needed.
For an initial index, cover the repository's material boundaries. For a refresh, use the last documented revision and actual changes to inspect affected claims and their consumers. Include uncommitted changes. When the baseline is missing or unreliable, broaden inspection rather than claiming incremental coverage.
Own each fact once
| File | Owns |
|---|---|
| REQ.md | Product intent, users, scope, requirements, acceptance criteria |
| CONTEXT.md | Architecture, repository map, contracts, constraints, operations |
| STATE.md | Current work, blockers, risks, next actions |
| TDD.md | Test strategy, actual commands, quality gates, missing coverage |
| DESIGN.md | Existing visual language, components, states, accessibility |
| DECISIONS.md | Dated decisions, alternatives, evidence, consequences, status |
Use the established primitive directory even when its set is incomplete. Add
missing documents there and preserve relative links. Use the repository root
only when no established location exists; resolve competing locations from
repository conventions before writing. Use assets/primitives/
for new files, removing scaffold placeholders. Link to the fact's owning file.
Mark non-UI projects explicitly in DESIGN.md. Keep STATE volatile and DECISIONS
durable; do not invent dates, owners, product intent, or historical decisions.
Discover and integrate
Work directly for small repositories or a narrow refresh. Delegate independent areas when that saves time or improves coverage; there is no required worker count. Read index-roles.md when splitting discovery. Its roles are coverage suggestions, not mandatory agents.
What ships with it
9 files 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 Changed · -87 lines · -35 tokens per session 0843d4dd8418
- 12d ago First seen · 171 lines · 86 tokens per session scan A 5aeb96b00f96
dale-index is a skill published in the GitHub repository lubluniky/dale (51 stars, last pushed 6d ago), licensed MPL-2.0. It adds 51 tokens to every session and 837 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-08-30.
Other skills, from other repositories
agent-creation-skill
Procedural guide for creating new agents from templates when project complexity requires delegation.
memory-fabric
Knowledge graph orchestration layer with entity extraction, natural language query parsing, deduplication (>85% similarity), and cross-reference boosting. Unifies search results ranked by recency, relevance, and authority. Use when designing memory retrieval, building entity graphs, or optimizing knowledge graph…
loop-graph
Compile one durable loop-graph run into executor, ledger, directives, ops, and supervisor artifacts under a dated .longgraph directory, then present copy-ready host prompts. Use directly for a custom multi-round shape with gated milestones, independent audit, cross-host execution, or durable state; focused sibling…
longgraph
Route and author durable long-horizon loop-graph runs. Use for multi-round work needing durable state, gated milestones, owner boundaries, host switching, or independent audit. Route code cleanup to /loop-converge, feature requirements to /loop-deliver, and evidence-backed solution comparison to /loop-research; use…
loop-converge
Author and optionally direct-launch a two-node loop-graph run whose North Star is code convergence — delete unused code, merge duplicates, reuse, slim. Use when the user invokes /loop-converge, or asks to loop on dead code, duplication, unused exports, DRY cleanup, or merging twin implementations. Starts the owner…
loop-deliver
Author and optionally direct-launch a two-node loop-graph run for implementing a product or engineering requirement through verified vertical slices. Use when a requested feature, integration, migration, or behavior change needs multiple rounds, durable acceptance proof, and independent audit. Not for code cleanup…