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/timmyagentic/cc-connect-next/claude-mdgit clone --depth 1 https://github.com/timmyagentic/cc-connect-nextWrote 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/timmyagentic/cc-connect-next/claude-md)<a href="https://agentmods.dev/instructions/timmyagentic/cc-connect-next/claude-md"><img src="https://agentmods.dev/badge/instructions/timmyagentic/cc-connect-next/claude-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.00053 | $0.00053 |
| Opus 5 | $0.00026 | $0.00026 |
| Sonnet 5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
cc-connect-next CLAUDE.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 5d 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
CC-Connect Development Guide
The canonical development instructions for every coding agent are in
AGENTS.md. Read that file in full before changing this repository;
if another instruction file disagrees with it, AGENTS.md wins.
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.
- 5d ago First seen · 6 lines · 53 tokens per session scan A 9c15efa3728c
cc-connect-next CLAUDE.md is an instructions file published in the GitHub repository timmyagentic/cc-connect-next (1 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session, about $0.0003 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
botmux CLAUDE.md
Claude Code instructions for deepcoldy/botmux, covering botmux, 构建 & 运行, bun 开发链路, worktree 的 nodemodules：共享还是独立（改前必读） and 编译态（单文件二进制）注意.
openlark AGENTS.md
AGENTS.md instructions for foxzool/openlark, covering openlark knowledge base, structure, where to look, conventions and 模块组织.
larksnap CLAUDE.md
Claude Code instructions for AmbroseX/larksnap, covering 基本约定, plan 文件管理, 开发规范, 根据场景动态调整顺序 and 文档写入.
Claude-to-IM-skill CLAUDE.md
Instructions for op7418/Claude-to-IM-skill, covering claude.md — project guidelines for claude-to-im-skill and replying to github issues.
lark-mcp-on-agentcore AGENTS.md
AGENTS.md instructions for ddpie/lark-mcp-on-agentcore, covering agents.md, project overview, setup & commands, project structure and code style.
lodestar AGENTS.md
AGENTS.md instructions for leviyuan/lodestar, covering lodestar 项目指引, 目录, 开发规则, 模块边界 and 运行中的 daemon.