Borrowing it
Nothing to install: this file belongs to sandraschi/glama-status-mcp. 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/sandraschi/glama-status-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/sandraschi/glama-status-mcpWrote 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/sandraschi/glama-status-mcp/agents-md)<a href="https://agentmods.dev/instructions/sandraschi/glama-status-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sandraschi/glama-status-mcp/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.00629 | $0.00629 |
| Opus 5 | $0.00315 | $0.00315 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
glama-status-mcp 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - glama-status-mcp
Agent protocols for Cursor, Windsurf, Claude Code, and any agentic IDE working in this repo.
Stack
- Language: Python 3.11+, FastMCP >= 3.4.2
- Package manager: uv
- Database: SQLite via aiosqlite
- Frontend: Vite + React + TypeScript
- Scraping: httpx + BeautifulSoup + lxml
- Linting: Ruff
Repo layout
glama-status-mcp/
├── src/glama_status_mcp/
│ ├── server.py FastMCP server + FastAPI HTTP mode
│ ├── scraper.py Async HTML scraper for glama.ai score pages
│ ├── database.py SQLite storage + delta engine
│ ├── models.py Pydantic models + fleet repo list
│ └── config.py Paths, constants, env vars
├── webapp/ Vite + React dashboard
├── data/ SQLite database (gitignored)
├── scripts/ Utility scripts (debug scrapers, scheduler)
├── tests/
├── justfile just install / serve / web / refresh
├── glama.json
├── llms.txt / llms-full.txt
├── PRD.md
└── CHANGELOG.md
MCP Tools
glama_status- Portmanteau: list, get, worst_tools, refresh, history, staleness, report, deltasglama_scores_summary- Grade distribution + per-repo statsglama_daily_report- Full markdown report
Ports
- Backend: 11072
- Frontend: 11073
Running
just install
just web # HTTP mode on :11072
just web-frontend # Vite dev on :11073
just refresh # Manual scrape + snapshot
Database schema
repos- Current per-repo scorestools- Per-tool TDQS dimension scoresscore_snapshots- One row per refresh runscore_history- Denormalized per-repo per-snapshot for fast deltasrefresh_log- Timestamps and errors per refreshfleet_repos- Tracked repos with author namespace
Key patterns
- Scraper uses polite HTTP (descriptive UA, 1s delay, BrightData fallback)
- Snapshot + delta engine: every refresh creates a snapshot; deltas compare latest two
- TDQS formula: 60% mean + 40% minimum across tools
- Grade thresholds: A >= 3.5, B >= 3.0, C >= 2.0, D >= 1.0, F < 1.0
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 · 70 lines · 629 tokens per session scan A d1d0539533bf
glama-status-mcp AGENTS.md is an instructions file published in the GitHub repository sandraschi/glama-status-mcp (2 stars, last pushed 7d ago), licensed MIT. It adds 629 tokens to every session, about $0.0031 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
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.