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 agentmods add skills/nguyenthanhtat/screen1-claude/data-loadingnpx skills add nguyenthanhtat/screen1-claude --skill data-loadinggit clone --depth 1 https://github.com/nguyenthanhtat/screen1-claudeWrote 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/nguyenthanhtat/screen1-claude/data-loading)<a href="https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/data-loading"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/data-loading.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.00000 | $0.03328 |
| Opus 5 | $0.00000 | $0.01664 |
| Sonnet 5 | $0.00000 | $0.00666 |
| Haiku 4.5 | $0.00000 | $0.00333 |
Grade A, and why
data-loading 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 5d 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BigQuery Data Loading & Export
Parent Skill: /bigquery
Path: /bigquery/data-loading
Purpose
Efficiently import data from various sources (GCS, local files, streaming) and export BigQuery results.
When to Use
Trigger automatically when:
- Keywords: load, import, export, CSV, JSON, Parquet, streaming
- User uploads file and mentions BigQuery
- User asks to "save query results"
Chat commands:
/bigquery/data-loading import CSV from gs://bucket/data.csv
/bigquery/data-loading load this file into table events
/bigquery/data-loading export query results to GCS
/bigquery/data-loading setup streaming for real-time data
Requirements
Verification
# Check GCS access
gsutil ls gs://your-bucket/
# Check BigQuery permissions
bq show your_project:dataset
Loading Patterns
Pattern 1: Load CSV from GCS
# Using bq CLI
bq load \
--source_format=CSV \
--skip_leading_rows=1 \
--autodetect \
dataset.table_name \
gs://bucket/data.csv
# Using Python client
from google.cloud import bigquery
client = bigquery.Client()
job_config = bigquery.LoadJobConfig(
source_format=bigquery.SourceFormat.CSV,
skip_leading_rows=1,
autodetect=True,
write_disposition='WRITE_TRUNCATE' # or WRITE_APPEND
)
uri = "gs://bucket/data.csv"
table_id = "project.dataset.table"
load_job = client.load_table_from_uri(
uri, table_id, job_config=job_config
)
load_job.result() # Wait for completion
print(f"Loaded {load_job.output_rows} rows")
Best Practices:
- Use
--autodetectfor schema inference (development only) - Specify explicit schema for production
- Use
WRITE_APPENDfor incremental loads - Partition target table by date if loading daily
Pattern 2: Load JSON (Newline-Delimited)
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.
- 5d ago First seen · 569 lines · 0 tokens per session scan A 87fa43b615dd
data-loading is a skill published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,328 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
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.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
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…
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…
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.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…