Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sfc-gh-dflippo/snowflake-dbt-demonpx agentmods add skills/sfc-gh-dflippo/snowflake-dbt-demo/autonomousWrote 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/sfc-gh-dflippo/snowflake-dbt-demo/autonomous)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/autonomous"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/autonomous/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/sfc-gh-dflippo/snowflake-dbt-demo/autonomous"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/autonomous.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.07023 |
| Opus 5.5 | $0.00000 | $0.02809 |
| Sonnet 5.5 | $0.00000 | $0.01405 |
| Haiku 4.5 | $0.00000 | $0.00702 |
Grade A, and why
migrate-objects-auto 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 — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Objects — Autonomous
On Entry IMPORTANT DO NOT SKIP
Tell the user:
Autonomous mode. I'll work the wave by giving each object its own subagent, which walks it the whole way — convert, deploy, tests, fixes — and I'll refill as they finish. I'll interrupt you only when an agent is stuck, when a dependency needs a human decision, and before any data moves. Say "stop" at any point and I'll let in-flight work land.
Step 0: Preflight
configure(project_dir=<project dir>, subagent_mode=true, snowflake_connection=<the configure connection the first prompt named>). Read the appended migration-status block. Bring the shared data infrastructure up:data_infrastructure(mode="up"). Relay itscost_reminder.status="not_ready"is not a green light — a first local bring-up runs every schema migration and can need more than one call, so follow itsremediationand callupagain until it reportsready. Once means one successful bring-up for the wave, not one call.- If
configure()reports setup is not finished, read ../../setup/SKILL.md then come back here.
subagent_mode attributes writes per Cortex conversation. Set it once here; it lasts the
life of the server and cannot be turned off. Cortex stamps identity on every MCP call —
do not pass agent_id. The parent hook injects 0000 while this latch is on: park a looping
object, reset a remediated transient failure, and relay non-terminal guidance.
Acknowledge unreviewed notes only in Step 3 (review), never in the dispatch
loop. Object-level outcomes stay parked for a person in an interactive session.
deploy, migrate_data, and validate_data are not binding-checked — keep
each agent on its own object.
Step 1: Ask how many subagents to run at once
Offer 2 / 4 / 6, recommend 4. State the
trade-off: more slots finish the wave faster, burn proportionally more tokens,
and produce more escalations competing for their attention. Call it N. Never
exceed it, and never quietly raise it.
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 · 527 lines · 0 tokens per session scan A e54fe6b690a5
migrate-objects-auto is a skill published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 7,023 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-09-10.
Other skills, from other repositories
360-feedback-system
360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
announcement-board
Announcement board: author, category, department, priority, audience, publish and expiry dates, status and acknowledgements, as CSV, SQL, JSON Schema or Notion on request. Use for internal notices.
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
record-gotchas
Capture surprises, workarounds, and rough edges hit while consuming the public surface of Prisma 8, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour…
product-direction
Judges feature requests, feature pull requests and your own proposals against a repository's written product direction, gives a cited verdict, and records each new no. Use when triaging, labelling or replying to a feature request or a feature pull request, including as an autonomous triage agent; when asked whether a…