Borrowing it
Nothing to install: this file belongs to IceWhaleTech/ZimaOS-Blue. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/IceWhaleTech/ZimaOS-Blue/main/AGENTS.mdgit clone --depth 1 https://github.com/IceWhaleTech/ZimaOS-BlueWrote 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/icewhaletech/zimaos-blue/agents-md)<a href="https://agentmods.dev/instructions/icewhaletech/zimaos-blue/agents-md"><img src="https://agentmods.dev/badge/instructions/icewhaletech/zimaos-blue/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.1 | $0.01778 | $0.01778 |
| Opus 5 | $0.00889 | $0.00889 |
| Sonnet 5 | $0.00356 | $0.00356 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
ZimaOS-Blue 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 8d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZimaOS-Blue Project
This is the canonical cross-agent instructions document for this repository.
Skills Reference
This project uses the following skills from .agents/skills/ and .agents/skill/:
Mobile Toggle UX Optimization (.agents/skill)
A focused design skill for optimizing crowded mobile toggle UI and making Auto mode clearly visible.
Usage: Read .agents/skill/mobile-toggle-ux/SKILL.md
Superpowers (obra/superpowers)
A complete software development workflow with composable skills.
Available Skills:
brainstorming- Socratic design refinementwriting-plans- Detailed implementation plansexecuting-plans- Batch execution with checkpointstest-driven-development- RED-GREEN-REFACTOR cyclesystematic-debugging- 4-phase root cause processverification-before-completion- Ensure fixes are completesubagent-driven-development- Fast iteration with two-stage reviewdispatching-parallel-agents- Concurrent subagent workflowsrequesting-code-review- Pre-review checklistreceiving-code-review- Responding to feedbackusing-git-worktrees- Parallel development branchesfinishing-a-development-branch- Merge/PR decision workflowwriting-skills- Create new skills
Usage: Read skill files from .agents/skills/superpowers/skills/<skill-name>/SKILL.md
Golang Best Practices (golang-best-practices)
Coding standards and best practices for Golang development.
Triggers:
- Database schema design
- Architecture decisions
- High-availability implementation
- Code review
- Bug fixing
- Performance optimization
- Command execution
- Goroutine management
Key Points:
- This project follows TDD (Test-Driven Development)
- Always write tests first
- No production code without a failing test
Usage: Read .agents/skills/golang-best-practices/SKILL.md
Planning with Files (planning-with-files)
Manus-style file-based planning for complex tasks. Creates persistent markdown files as "working memory on disk."
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.
- 8d ago First seen · 140 lines · 1,778 tokens per session scan A feb8ee153608
ZimaOS-Blue AGENTS.md is an instructions file published in the GitHub repository IceWhaleTech/ZimaOS-Blue (25 stars, last pushed 4mo ago), licensed MIT. It adds 1,778 tokens to every session, about $0.0089 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.