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 rudderlabs/rudder-agent-skills --skill rudder-profiles-updategit clone --depth 1 https://github.com/rudderlabs/rudder-agent-skillsWrote 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/rudderlabs/rudder-agent-skills/rudder-profiles-update)<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-profiles-update"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-profiles-update/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/rudderlabs/rudder-agent-skills/rudder-profiles-update"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-profiles-update.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.00062 | $0.02431 |
| Opus 5 | $0.00031 | $0.01215 |
| Sonnet 5 | $0.00012 | $0.00486 |
| Haiku 4.5 | $0.00006 | $0.00243 |
Grade A, and why
rudder-profiles-update 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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RudderStack Profiles Project Update
Modify an existing Profiles project carefully. Always understand the current state first, classify risk, and validate after each change.
Workflow
- Read current state — Read all YAML files, run
pb show models, runpb compile. - Fix first — If compile already fails, fix the existing project before introducing new changes.
- Classify the change — Determine risk level before making edits (see table below).
- Make one change at a time — Edit, then
pb compile. Do not batch multiple changes before validating. - Offer a run — Only after compile is green and user confirms.
Change Risk Classification
| Change Type | Risk | Key Concern |
|---|---|---|
| Add new entity_var | Safe | Must aggregate if has from |
| Add new input source | Safe | Verify table/columns exist via describe_table() |
| Add new id_type | Moderate | Affects identity resolution graph |
Add feature view (using_ids) |
Safe | Re-keys existing output; needs an id_type already on the entity |
| Add entity cohort | Moderate | Filter features must exist in the parent var_group; re-run to materialize |
| Add/modify sql_template model | Moderate | Pongo2 + DeRef dependencies; single_sql can't take a top-level WITH; materialization choice affects cost |
| Add optimizations.yaml flag | Safe | Enable one at a time and confirm output is unchanged |
| Modify existing entity_var | Moderate | Downstream refs may break; invalidates incremental checkpoints |
| Add propensity model | Moderate | Date handling rules change completely (see below) |
| Add attribution model | Moderate | Needs a separate campaign entity + campaign id_stitcher first (see below) |
| Remove entity_var or input | Breaking | Must scan all refs first; warn about downstream consumers |
| Change entity or id_stitcher | Breaking | Full re-run required; all checkpoints invalidated |
Before writing any change:
- Name the risk class.
- Name the expected blast radius.
- Tell the user what validation will prove the change is safe.
What ships with it
11 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.
- references/approximate-aggregators.md 3.0 KB
- references/attribution-yaml-template.md 5.5 KB
- references/change-risk-classification.md 2.3 KB
- references/cohorts-and-feature-views.md 4.1 KB
- references/compound-aggregator-cookbook.md 4.9 KB
- references/incremental-migration.md 8.3 KB
- references/known-gotchas.md 5.4 KB
- references/optimizations-and-macros.md 3.6 KB
- references/propensity-yaml-template.md 4.4 KB
- references/sql-template-models.md 3.3 KB
- references/warehouse-shims.md 4.5 KB
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.
- 12d ago First seen · 138 lines · 62 tokens per session scan A 69905b52870f
rudder-profiles-update is a skill published in the GitHub repository rudderlabs/rudder-agent-skills (18 stars, last pushed 8d ago), licensed MIT. It adds 62 tokens to every session and 2,431 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
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
migrate-postgres-tables-to-hypertables
Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
find-hypertable-candidates
Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. Trigger when user asks to: Analyze database tables for hypertable conversion potential Identify time-series or event tables in an existing schema Evaluate if a table would…