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 ForgeyClap/claude-forge --skill forge-datagit clone --depth 1 https://github.com/ForgeyClap/claude-forgeWrote 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/forgeyclap/claude-forge/forge-data)<a href="https://agentmods.dev/skills/forgeyclap/claude-forge/forge-data"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-data/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/forgeyclap/claude-forge/forge-data"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-data.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.00000 | $0.01372 |
| Opus 5.5 | $0.00000 | $0.00549 |
| Sonnet 5.5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
forge-data 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 20d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge playbook — Data engineering / ETL / dbt
Do not duplicate ECC skills — defer to: systematic-debugging (pipeline failures), /test-coverage (transform test coverage), learn-codebase / forge-deeplearn (prime an existing warehouse before touching it). This file is orchestration only.
A data pipeline's job is to be trustworthy and repeatable, not just to "run once". The failure mode here is silent: a load that half-succeeds, a duplicate on retry, or a schema change upstream that quietly corrupts a downstream mart while every job still shows green. Treat the warehouse as the product.
Hard rules
- Schema contracts at every boundary. Source and model outputs declare an explicit, enforced schema (dbt model
contracts: enforced, or an explicit column/type check on load). A schema-drift upstream fails the run loudly — never silently coerces or drops columns. - Idempotent + incremental. A rerun produces the same result — no duplicated rows. Incremental loads use a stable unique key (
merge/upsert) and a watermark/high-water-mark with a look-back window to handle late-arriving data;append-only without a dedupe key is banned. Backfills are explicit, bounded, and stated (date range / partition), never an unbounded full-table rewrite by accident. - Data-quality tests are part of "done". Not-null / unique / accepted-values / referential (
relationships) tests on key columns, plus a freshness check and a row-count/volume sanity check. A pipeline with zero tests is not shippable. - Lineage is documented. The DAG / column-level lineage is generated or written down (dbt docs / a lineage diagram). No orphan models, no undocumented hop that only lives in someone's head.
- No PII leakage. PII is classified up front; masked, hashed, or tokenized where it lands; never written to logs, never committed to the repo, and access-scoped in the warehouse. Minimize what you collect and keep.
- Dead-letter for validation failures. Records that fail validation go to a dead-letter table or file with the original data, the error, and a timestamp — never silently dropped.
- Reproducible runs. Warehouse/profile credentials in env (never in
profiles.ymlor committed), dependencies pinned, SQL/seeds versioned in git, transformations deterministic (nonow()-driven nondeterminism baked into stored results without a reason). The same code + same input → the same table.
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.
- 20d ago Changed · +1 lines · -50 tokens per session 0753645f3cdc
- 1mo ago First seen · 39 lines · 50 tokens per session scan A f1058a652373
forge-data is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,372 tokens. 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-31.
Other skills, from other repositories
qdrant
Vector search engine for production RAG systems.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
pyspark-etl
Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg. Use when writing or reviewing PySpark jobs, designing joins and window functions, working with map/array higher-order functions, or building idempotent cumulative/snapshot table merges.
data-lake-platform
Designs lakehouse platforms across Iceberg, Delta, Hudi, and Paimon. Use when choosing catalogs, CDC paths, query engines, governance, or cost controls.