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 instructions/carbonshow/intent-fluid/gemini-mdgit clone --depth 1 https://github.com/carbonshow/intent-fluidWrote 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/instructions/carbonshow/intent-fluid/gemini-md)<a href="https://agentmods.dev/instructions/carbonshow/intent-fluid/gemini-md"><img src="https://agentmods.dev/badge/instructions/carbonshow/intent-fluid/gemini-md.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.00391 | $0.00391 |
| Opus 5 | $0.00196 | $0.00196 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
intent-fluid GEMINI.md 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 3d 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.
What it actually says
Intent-Fluid Project Context
Project Overview
Intent-Fluid is a curated collection of AI SKILLs designed to bridge the gap between high-level concepts and execution. Its core philosophy is "Intent Over Implementation," aiming to reduce the friction of coding by leveraging AI to handle low-level boilerplate, APIs, and configuration, thereby allowing creators to maintain a state of "Flow".
Skill Directory Structure
Skills live under skills/. Each skill is a directory containing a SKILL.md file with YAML frontmatter (name, description, version, author, tags, platforms) followed by the skill prompt body. The AI platform scans skills/*/SKILL.md to discover available skills and uses the description field to determine when to activate each skill.
Current skills:
skills/surge/— Autonomous iterative delivery (PRD → analyze → research → design → implement → QA → retro)
Key Files & Directories
README.md: Contains the project manifesto, core philosophy, and use cases./skills: A library of structured prompts, chain-of-thought methodologies, and agent configurations. Each skill has aSKILL.mdmanifest.docs/SKILL_SPEC.md: Skill developer specification — format, naming, and validation rules.docs/SKILL_TEMPLATE.md: Quick-start template for new skill authors.scripts/validate-skill.sh: Automated compliance checker for skill directories.LICENSE: MIT License file.
Usage
This repository serves as a skill library for AI-assisted development:
- Study Skills: Read existing skills under
skills/to understand structured prompt design. - Create Skills: Follow
docs/SKILL_SPEC.mdanddocs/SKILL_TEMPLATE.mdto author new skills. - Validate: Run
bash scripts/validate-skill.sh skills/<name>before publishing.
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.
- 3d ago First seen · 25 lines · 391 tokens per session scan A 9ea6ef5acce5
intent-fluid GEMINI.md is an instructions file published in the GitHub repository carbonshow/intent-fluid (6 stars, last pushed 3mo ago), licensed MIT. It adds 391 tokens to every session, about $0.0020 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-31.
Other instructions, from other repositories
factory CLAUDE.md
Instructions for watt-mind/factory: Claude, please refer to AGENTS.md and docs/protocol.md for the primary repository context, architecture, commands, operational rules, and tracker issue management standards.
factory GEMINI.md
Instructions for watt-mind/factory: Gemini, please refer to AGENTS.md and docs/protocol.md for the primary repository context, architecture, commands, operational rules, and tracker issue management standards.
Maestro CLAUDE.md
Instructions for aaryansinha16/Maestro, covering maestro — claude.md, project identity, core operating principles, how it works and the conductor (brain).
Maestro AGENTS.md
Instructions for aaryansinha16/Maestro, covering maestro — agents.md, purpose, before any task, task patterns and when adding a new feature to the conductor.
factory AGENTS.md
Instructions for watt-mind/factory, covering commands, agent operating floor, handoff, never auto-merge and protected branches.
atelier AGENTS.md
AGENTS.md instructions for duanecilliers/atelier, covering agents.md, what this is, commands, the seam contract - the #1 rule and architecture.