Borrowing it
Nothing to install: this file belongs to RipeMangoBox/BITE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RipeMangoBox/BITE/main/.claude/skills/papers-build-index/SKILL.mdgit clone --depth 1 https://github.com/RipeMangoBox/BITEWrote 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/ripemangobox/bite/papers-build-index)<a href="https://agentmods.dev/skills/ripemangobox/bite/papers-build-index"><img src="https://agentmods.dev/badge/skills/ripemangobox/bite/papers-build-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/ripemangobox/bite/papers-build-index"><img src="https://agentmods.dev/badge/skills/ripemangobox/bite/papers-build-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.01010 |
| Opus 5.5 | $0.00028 | $0.00404 |
| Sonnet 5.5 | $0.00014 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
papers-build-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 1mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Index
What this skill does
Regenerates the local paper index under obsidian-vault/index/.
Inputs:
obsidian-vault/paper_list.csvwhen present. This is the paper inventory.obsidian-vault/analysis/**/*.mdfrontmatter when present. This is evidence and enrichment, not a required database.
Outputs:
obsidian-vault/index/index.jsonlobsidian-vault/index/paper_index.mdobsidian-vault/index/_AllPapers.md- aggregate pages under:
by_dataset/by_method/by_topic/by_venue_year/
The builder does not require the platform database.
obsidian-vault/index/README.md is a public placeholder for the generated
directory and should not be overwritten with local/private index contents.
Aggregate navigation entry files use explicit dimension names:
by_topic/topic_index.md, by_method/method_index.md,
by_dataset/dataset_index.md, and
by_venue_year/venue_year_index.md.
Venue and year navigation is merged into venue_year labels such as
ICLR_2026; the builder does not generate separate by_venue/ or by_year/
indexes.
by_topic/ uses coarse top-level research areas derived from category,
topics, topic/... tags, or path hints. Nested topic tags are intentionally
folded into their first segment so the navigation does not fragment.
topic/<venue_year> tags in analysis frontmatter are treated as venue/year
metadata, not research-topic taxonomy.
by_method/ uses normalized method-family labels derived from method names,
tags, title, core_operator, and primary_logic. Exact per-paper method names
remain in index.jsonl under methods for precise search and comparison.
by_dataset/ lists only dataset values that appear in at least two papers so
single-paper experiment slices do not dominate Obsidian navigation. The full
per-paper dataset field remains in index.jsonl. Dataset display values are
normalized to dataset names; parenthesized model, split, seed, resolution, and
other experiment-setting details are stripped.
Generated paper entries are nested Obsidian list items, not one-line entries
joined with punctuation separators. Each entry places the analysis note link on
the parent bullet and PDF/topics/method groups/methods/datasets on child
bullets.
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.
- 1mo ago First seen · 99 lines · 71 tokens per session scan A 0ddc4f464d4e
papers-build-index is a skill published in the GitHub repository RipeMangoBox/BITE (62 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,010 once invoked, about $0.0003 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-30.
Other skills, from other repositories
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
wiki-status
Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.