Borrowing it
Nothing to install: this file belongs to mahatab/synode-council-of-ai-agents. 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/mahatab/synode-council-of-ai-agents/main/CLAUDE.mdgit clone --depth 1 https://github.com/mahatab/synode-council-of-ai-agentsWrote 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/mahatab/synode-council-of-ai-agents/claude-md)<a href="https://agentmods.dev/instructions/mahatab/synode-council-of-ai-agents/claude-md"><img src="https://agentmods.dev/badge/instructions/mahatab/synode-council-of-ai-agents/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/mahatab/synode-council-of-ai-agents/claude-md"><img src="https://agentmods.dev/badge/instructions/mahatab/synode-council-of-ai-agents/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00814 | $0.00814 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
synode-council-of-ai-agents 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 13d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synode - Council of AI Agents
Project Overview
Tauri 2 desktop app (macOS + Windows) that orchestrates multi-AI council discussions. React 19 + TypeScript frontend, Rust backend.
Workspace Structure
Cargo.toml (workspace root)
├── src-tauri/ — Tauri desktop app (v0.3.1)
├── crates/council-core/ — Shared library: AI providers, keychain, sessions, settings
└── crates/telegram-bot/ — Telegram bot integration (v0.1.0)
Current Branch: claude/clever-bartik (worktree)
What's Been Built (Telegram Bot - Phases 1-5 complete)
- council-core extracted from src-tauri as shared library
- telegram-bot crate with full functionality:
handlers.rs— 8 slash commands: /start, /council, /chat, /models, /sessions, /settings, /stop, /helpcouncil.rs— Full council orchestration (ported from councilStore.ts)direct_chat.rs— 1-on-1 chat with any model, fuzzy name resolutionformatting.rs— Markdown-to-Telegram-HTML converter, typing indicators, message splittingstate.rs— AppState with keychain, settings, per-chat mode trackingmain.rs— Standalone binary entry point (teloxide dispatcher)
- All compilation errors fixed, workspace builds clean
- Tested with live Telegram bot
Architecture Decision: Option A — Embed Bot in Desktop App
Decided: The Telegram bot will be embedded in the Tauri desktop app, NOT run as a separate process.
How it works:
- User creates a bot via @BotFather on Telegram, gets a token
- User opens Synode desktop app → Settings → Telegram Integration
- User pastes token and toggles "Enable Telegram Bot"
- Tauri app spawns the bot as a background tokio task (same process)
- Bot shares the same AppState (keychain, settings, sessions) as the desktop app
- Bot stops when the app closes
The standalone binary (council-telegram-bot) is kept as an alternative for power users wanting server deployment.
What Needs to Be Implemented Next
- Refactor telegram-bot crate — expose a
start_bot(token, app_state)library function alongside the binary - Add Tauri command —
start_telegram_bot/stop_telegram_botcommands callable from frontend - Settings UI — Add "Telegram Integration" section in Settings with token input and enable/disable toggle
- Lifecycle management — Start/stop bot based on settings, persist token, auto-start on app launch if previously enabled
- Documentation — TELEGRAM_BOT.md, update README, update ARCHITECTURE.md
- CI/CD — Add telegram-bot to CI checks, optionally build standalone binary in release workflow
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.
- 13d ago First seen · 58 lines · 814 tokens per session scan A 5c6aff0bdf1c
synode-council-of-ai-agents CLAUDE.md is an instructions file published in the GitHub repository mahatab/synode-council-of-ai-agents (59 stars, last pushed 5mo ago), licensed MIT. It adds 814 tokens to every session, about $0.0041 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
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.
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).
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).