Borrowing it
Nothing to install: this file belongs to flancian/agora-server. 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/flancian/agora-server/main/GEMINI.mdgit clone --depth 1 https://github.com/flancian/agora-serverWrote 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/flancian/agora-server/gemini-md)<a href="https://agentmods.dev/instructions/flancian/agora-server/gemini-md"><img src="https://agentmods.dev/badge/instructions/flancian/agora-server/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.1 | $0.12497 | $0.12497 |
| Opus 5 | $0.06248 | $0.06248 |
| Sonnet 5 | $0.02499 | $0.02499 |
| Haiku 4.5 | $0.01250 | $0.01250 |
Grade A, and why
agora-server 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.
How it starts
The opening of the file, as written. The whole thing — 726 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This file provides a summary of my core understanding of the Agora project, which I use as my primary context for our sessions.
For a detailed plan of future work, see [[ROADMAP.md]]. For a log of completed work, see [[DONE.md]]. For essays and poems on the project's philosophy, see [[PHILOSOPHY.md]].
Memories & Mandates
- Feature Flag Protocol: Always enable new feature flags in
LocalDevelopmentConfigfirst. Never enable inAlphaConfigorProductionConfigwithout explicit user instruction and prior local verification. - Git Operations: The user prefers to handle commits themselves, or explicitly approve them. Always
git statusandgit diffbefore asking. NEVER usegit add .orgit add -Aunder any circumstances, as other agents might be operating concurrently. Always explicitly list the exact files to add:git add <file1> <file2>. - Development: Run
npm run buildafter TypeScript changes. Do not use./run-dev.sh; the user manages the server. - Tone: Be direct and technical. Use metaphors sparingly (e.g., for "Federation").
Understanding the Agora (as of 2025-09-21)
This is a summary of my understanding of the project's philosophy and technical principles based on our collaboration.
The Agora of Flancia's Intents (The "Why")
The project's goal is to create a Free Knowledge Commons with a focus on:
- Connecting Digital Gardens: Weaving together individual, user-owned collections of notes into a larger whole.
- Collaborative Problem-Solving: Building a space where knowledge is not just stored but actively used and composed into tools.
- Low Barrier to Contribution: Prioritizing simple, durable formats (like plain text files) to make it easy for anyone to participate.
- Playful Experimentation: Fostering a delightful and evolving user experience.
The Agora Protocol (The "How")
The protocol is a set of architectural patterns that enable the Agora's vision:
- Decentralization: The filesystem is the ultimate source of truth. The server is a lens, not a silo.
- Nodes are Concepts, Subnodes are Utterances: A key distinction where abstract topics (
[[Calculus]]) are composed of concrete contributions (@user/calculus-notes.md). - Composition over Centralization: Nodes are built by pulling and combining content from other, more specialized nodes (e.g.,
[[170]]pulling from[[calc/170]]). - Everything Has a Place (No 404s): Every possible query resolves to a node, turning dead ends into invitations to contribute.
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 · 726 lines · 12,497 tokens per session scan A 754c99638909
agora-server GEMINI.md is an instructions file published in the GitHub repository flancian/agora-server (64 stars, last pushed today), licensed Apache-2.0. It adds 12,497 tokens to every session, about $0.0625 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-09-03.
Other instructions, from other repositories
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).
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.
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).
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.