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 ai-analyst-lab/ai-analyst --skill archaeologygit clone --depth 1 https://github.com/ai-analyst-lab/ai-analystWrote 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/ai-analyst-lab/ai-analyst/archaeology)<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/archaeology"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/archaeology/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/ai-analyst-lab/ai-analyst/archaeology"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/archaeology.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.00100 | $0.01315 |
| Opus 5 | $0.00050 | $0.00658 |
| Sonnet 5 | $0.00020 | $0.00263 |
| Haiku 4.5 | $0.00010 | $0.00131 |
Grade A, and why
archaeology 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- archaeology — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Query Archaeology
Purpose
Retrieve proven SQL patterns, table cheatsheets, and join patterns from the query archaeology store so agents reuse validated work instead of writing SQL from scratch. The skill also defines the store's local write path: after a validated analysis, the final SQL is curated back into the store (the Writer Convention below), which is what makes the retrieval loop close.
When to Use
- Automatically before any analysis agent writes SQL (pre-flight step)
- Manually when the user asks about known patterns for a table or join
- After a validated analysis, to curate the proven SQL (Writer Convention)
Instructions
Step 1: Check the Index
Read .knowledge/query-archaeology/curated/index.yaml. Parse counters:
cookbook_entries, table_cheatsheets, join_patterns.
If all three are zero (or the file is missing), stop here. Return nothing and do not mention archaeology to the user.
Step 2: Identify Search Terms
From the current analysis context, extract:
- Table names the agent is about to query (e.g.,
orders,events) - Query intent tags (e.g.,
funnel,retention,revenue,cohort)
Step 3: Search the Three Stores
Search each store that has entries (per index counts). Match using
case-insensitive substring -- order matches orders, order_items.
3a. Cookbook (curated/cookbook/*.yaml)
For each file, check:
tablesarray -- any element contains a search table name as substring?tagsarray -- any element matches a query intent tag?
Extract on match: title, sql, tables, tags, and any caveats/notes.
3b. Table Cheatsheets (curated/tables/*.yaml)
For each file, check:
table_namecontains a search table name as substring?
Extract on match: table_name, grain, primary_key, common_filters,
gotchas, common_joins.
3c. Join Patterns (curated/joins/*.yaml)
For each file, check:
tablesarray -- at least two elements match search table names?- If only one search table, match if
tablescontains it as substring.
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.
- 2d ago First seen · 139 lines · 100 tokens per session scan A 2ced0eccef8e
archaeology is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (298 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 1,315 once invoked, about $0.0005 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-12.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.