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 CodeInfinity1/Stram --skill airtable-operationsgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/airtable-operations)<a href="https://agentmods.dev/skills/codeinfinity1/stram/airtable-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/airtable-operations/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/codeinfinity1/stram/airtable-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/airtable-operations.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.00033 | $0.00502 |
| Opus 5.5 | $0.00013 | $0.00201 |
| Sonnet 5.5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
airtable-operations 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airtable Operations
Purpose
Use Airtable as a structured data surface when a native adapter exists or is being designed. The skill helps define tables, filters, records, and upserts safely.
When To Use
Use for Airtable bases, record lookup, filters, updates, upserts, sync planning, and API wrapper design.
Inputs And Evidence
- Base/table IDs, fields, filters, records, desired mutation, and auth status.
- Provided CSV/data or API docs.
Tool Map
tool_searchcapability_surfaceairtable_operation_prepareapi_operation_inspectagent-api-integrationpython_interpreterwrite_note
Workflow
- Determine the explicit Airtable operation: list, create, update, upsert, or delete records.
- Define the table schema, base ID, table ID/name, filters, records, and upsert key fields.
- Use
airtable_operation_prepareto create a local operation artifact with endpoint, method, payload, approval requirement, andnot_executedstatus. - Use
api_operation_inspectbefore reporting the artifact or handing it to a future live adapter. - Require approval before mutating records.
- Verify affected record IDs and fields through a future approved live adapter; a prepared artifact is not a live change.
Native Implementation Boundaries
- Do not import external reference Airtable scripts.
- Implement Airtable as Stram-owned tools with tests.
- Keep tokens in secret storage.
- The current native adapter prepares and inspects operation artifacts; live Airtable mutation must be added as a separate approval-gated tool.
Safety And Approval
- Airtable records may be business-critical.
- Updates, deletes, and upserts need approval.
- Avoid broad filters that mutate too many records.
Verification
- Prepared operations need saved path plus
api_operation_inspectevidence. - Record changes need IDs and response evidence.
- Missing adapter status should be explicit.
Failure Modes
- Upserting duplicates because key fields were unclear.
- Updating the wrong base/table.
- Claiming API integration from a drafted plan.
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 · 68 lines · 33 tokens per session scan A 8ff91d51854b
airtable-operations is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 502 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
omh-relational-db
This is an OMH relational-db workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
data-governance
Use this skill when designing or reviewing data governance: schema ownership, PII handling, retention, lineage, access policy, and migration safety for services and data stores. Triggers: user says "data governance", "PII", "schema ownership", "retention policy", "data lineage", "migration safety".
backup-recovery
Design and verify backups and restoration for owned databases, files and application state. Use when preparing recovery, migrating data or testing backups; protect the source and prove restore into an isolated destination before calling recovery ready.
database-development
Implement database access, models and queries with explicit consistency, transactions and bounded results. Use when working with SQL, document databases, Redis or ORM clients; use database-migrations for schema rollout/recovery and verify actual engine/client compatibility.
agent-database-expert
Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.