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/tryghost/ghost/tinybird-cli-guidelinesnpx skills add TryGhost/Ghost --skill tinybird-cli-guidelinesgit clone --depth 1 https://github.com/TryGhost/GhostWhat 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.00034 | $0.00382 |
| Opus 5 | $0.00017 | $0.00191 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
tinybird-cli-guidelines 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 today.
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.
What it actually says
Tinybird CLI Guidelines
Guidance for using the Tinybird CLI (tb) for local development, deployments, data operations, and workspace management.
When to Apply
- Running any
tbcommand - Choosing a development workflow (local, branch, or cloud)
- Local development with Tinybird Local
- Branch development with Tinybird Cloud branches
- Building and deploying projects
- Setting up CI/CD pipelines
- Appending, replacing, or deleting data
- Managing tokens and secrets via CLI
- Generating mock data
- Running tests
Rule Files
rules/development-workflows.mdrules/cli-commands.mdrules/build-deploy.mdrules/local-development.mdrules/branch-development.mdrules/ci-cd.mdrules/data-operations.mdrules/append-data.mdrules/mock-data.mdrules/tokens.mdrules/secrets.md
Quick Reference
- CLI 4.0 workflow: configure
dev_modeonce, then use plaintb buildandtb deploy. tb buildtargets your configured development environment (branchorlocal) in tinybird.config.json.tb deploytargets Tinybird Cloud production.- Use
--cloud/--local/--branchonly as explicit manual overrides. - Use
tb infoto check CLI context. - Use
tb endpoint data <pipe>to test endpoints (nottb pipe data). - Never invent commands or flags; run
tb <command> --helpto verify.
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.
- rules/append-data.md 737 B
- rules/branch-development.md 3.8 KB
- rules/build-deploy.md 2.2 KB
- rules/ci-cd.md 6.0 KB
- rules/cli-commands.md 5.7 KB
- rules/data-operations.md 1.9 KB
- rules/development-workflows.md 3.0 KB
- rules/local-development.md 1.9 KB
- rules/mock-data.md 1.2 KB
- rules/secrets.md 786 B
- rules/tokens.md 1.4 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.
- today First seen · 46 lines · 34 tokens per session scan A 1da70d3aab38
tinybird-cli-guidelines is a skill published in the GitHub repository TryGhost/Ghost (55,095 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 382 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-09-01.
Other skills, from other repositories
write-concept
Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines.
seo-review
Perform a focused SEO audit on JavaScript concept pages to maximize search visibility, featured snippet optimization, and ranking potential.
fact-check
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation.
resource-curator
Find, evaluate, and maintain high-quality external resources for JavaScript concept documentation, including auditing for broken and outdated links.
test-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines.
concept-workflow
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review.