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/pipefy/ai-toolkit/pipefy-database-tablesnpx skills add pipefy/ai-toolkit --skill pipefy-database-tablesgit clone --depth 1 https://github.com/pipefy/ai-toolkitWrote 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/pipefy/ai-toolkit/pipefy-database-tables)<a href="https://agentmods.dev/skills/pipefy/ai-toolkit/pipefy-database-tables"><img src="https://agentmods.dev/badge/skills/pipefy/ai-toolkit/pipefy-database-tables.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 | $0.00048 | $0.01702 |
| Opus 5 | $0.00024 | $0.00851 |
| Sonnet 5 | $0.00010 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
pipefy-database-tables 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 4d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Tables
Tables, records (rows), schema columns (table fields), and attachments for Pipefy Database Tables. 17 MCP tools.
Cross-cutting patterns
- Same conventions as pipe building:
introspect_typeon inputs such asCreateTableFieldInput/UpdateTableFieldInput,debug=trueon mutations. - Pagination:
get_table_recordsandfind_recordssupportfirst/after. With the unified MCP envelope, read top-levelpagination.has_moreandpagination.end_cursor(andpagination.page_size) and passafter=end_cursorfor the next page (default page size is 50). find_recordsover paginatedget_table_recordswhen you know the field value. Onefind_recordscall with acolumn_id/search_valuefilter beats N pages ofget_table_records.- Legacy mutation envelope. Several table mutation tools still return the GraphQL operation name as a nested key under
result(for exampleresult.createTableRecord). Read the payload inside that key; shape may differ from tools that already use the unified envelope.
Table operations
| Tool (MCP) | CLI | Read-only | Purpose |
|---|---|---|---|
get_tables |
pipefy table list |
Yes | List database tables by org. |
search_tables |
pipefy table list --search |
Yes | Search tables by name. |
get_table |
pipefy table get <id> |
Yes | Table metadata and field schema. |
create_table |
pipefy table create |
No | Create a new database table. |
update_table |
pipefy table update <id> |
No | Rename or change settings. |
delete_table |
pipefy table delete <id> |
No | Two-step destructive. |
Table field (schema column) operations
| Tool (MCP) | CLI | Purpose |
|---|---|---|
create_table_field |
pipefy table field create <table_id> --label <name> --type <type> |
Add a column to a table schema. |
update_table_field |
pipefy table field update <field_id> --table <table_id> --label <name> |
Rename or change column settings (--description, --required, --options). |
delete_table_field |
pipefy table field delete <field_id> --table <table_id> |
Two-step destructive. Requires table_id. |
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.
- 4d ago First seen · 127 lines · 48 tokens per session scan A 430c4e860521
pipefy-database-tables is a skill published in the GitHub repository pipefy/ai-toolkit (45 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 1,702 once invoked, about $0.0002 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
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
azure-resource-manager-postgresql-dotnet
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for…
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
supabase-postgres-best-practices
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the…
aws-cloudformation-dynamodb
Provides AWS CloudFormation patterns for DynamoDB tables, GSIs, LSIs, auto-scaling, and streams. Use when creating DynamoDB tables with CloudFormation, configuring primary keys, local/global secondary indexes, capacity modes (on-demand/provisioned), point-in-time recovery, encryption, TTL, and implementing template…