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/shrwnsan/clix-dev-flow/agents-mdgit clone --depth 1 https://github.com/shrwnsan/clix-dev-flowWrote 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/shrwnsan/clix-dev-flow/agents-md)<a href="https://agentmods.dev/instructions/shrwnsan/clix-dev-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/shrwnsan/clix-dev-flow/agents-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.00753 | $0.00753 |
| Opus 5 | $0.00377 | $0.00377 |
| Sonnet 5 | $0.00151 | $0.00151 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
clix-dev-flow AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines
This document provides essential guidelines for AI agents working with the Dev Flow extension project development and maintenance.
Purpose: This file documents how AI agents should interact with and contribute to this Dev Flow project itself (development, documentation, code reviews, etc.).
Extension Version: 1.1.0
Related Documentation:
- GEMINI.md - Gemini CLI extension context (loaded automatically by Gemini CLI)
- README.md - User-facing documentation and command reference
Project Structure
dev-flow/
├── README.md # User-facing documentation
├── AGENTS.md # This file - AI agent guidelines
├── GEMINI.md # Gemini CLI extension context
├── EXAMPLES.md # Usage examples
├── CHANGELOG.md # Version history
├── NOTICE # Attribution notice
├── gemini-extension.json # Extension configuration
├── commands/dev/ # Command definitions (.toml files)
└── tasks/ # Created during runtime (not tracked)
Core Extension Workflow
The Dev Flow extension follows a simple three-step process for users:
- Plan (
/dev:create-prd) - Generate feature planning documents - Design (
/dev:generate-tasks) - Create task breakdowns - Build (
/dev:process-task-list) - Execute implementation
Agent Guidelines for Project Work
When Contributing to This Project
- Focus on maintaining simplicity - this is intentionally a lightweight CLI extension
- Keep documentation clear and concise
- Test changes thoroughly before committing
- Follow established patterns in the codebase
Documentation Updates
- Update README.md for user-facing changes
- Update GEMINI.md for extension context changes
- Update AGENTS.md when changing how agents should work with the project
- Keep CHANGELOG.md updated with version changes
Code Reviews and Development
- Prioritize user experience and simplicity
- Ensure commands work reliably across different environments
- Test with actual Gemini CLI installation when possible
- Verify documentation accuracy after changes
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 · 99 lines · 753 tokens per session scan A b10327b340b5
clix-dev-flow AGENTS.md is an instructions file published in the GitHub repository shrwnsan/clix-dev-flow (10 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 753 tokens to every session, about $0.0038 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.