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.
git clone --depth 1 https://github.com/guorunjie/skillpack-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/rules/guorunjie/skillpack-forge/data-pipeline-demo)<a href="https://agentmods.dev/rules/guorunjie/skillpack-forge/data-pipeline-demo"><img src="https://agentmods.dev/badge/rules/guorunjie/skillpack-forge/data-pipeline-demo.svg" alt="Measured on agentmods" 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.00160 | $0.00160 |
| Opus 5 | $0.00080 | $0.00080 |
| Sonnet 5 | $0.00032 | $0.00032 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
data-pipeline-demo 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 6d 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.
What it actually says
data-pipeline-demo
Generated from skillpack.yaml by Skillpack Forge.
Data pipeline workflows for extraction, validation, transformation, and reporting.
Principles
- Preserve raw inputs and keep derived outputs separate
- Validate schemas, row counts, checksums, and representative samples
- Run transformations on a narrow sample before full pipeline execution
- Record data assumptions, freshness, and known quality gaps
Commands
- install:
npm install - test:
npm test - data:validate:
npm run data:validate - data:transform:
npm run data:transform - data:report:
npm run data:report
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.
- 6d ago First seen · 26 lines · 160 tokens per session scan A 6a152304eb80
data-pipeline-demo is a cursor rule published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 3mo ago), licensed MIT. It adds 160 tokens to every session, 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-31.
Other cursor rules, from other repositories
langchain
Apply when building LangChain pipelines, LCEL chains, agents, or retrieval-augmented generation systems.
skill-creator
Create, edit, evaluate, and debug the skills in this repo, including running their evals and fixing a description that fails to trigger. Use when user says 'help me build a new skill', 'add a skill for X', 'run the evals for the tf skill', 'run the behavioral evals', 'my skill is not triggering', 'fix this skill's…
tf-plan
Review a Terraform plan before applying it: destroys and replacements of data-bearing resources, secrets readable in plan output, out-of-band drift, blast radius, and whether the apply is bound to the plan you actually reviewed. Use when user says 'review my plan', 'is this plan safe to apply', 'check tfplan', 'what…
task
Task execution rules for Glitch Payment Gateway engineering work — verification gates, plan node, self-improvement loop.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.