What is glama-status-mcp AGENTS.md?

Project instructions for glama-status-mcp, a Python service that collects and stores scores from Glama.ai pages and displays them in a web dashboard. It uses SQLite, a small local database, for storing results.

Developing or maintaining the scraper, score database, change tracking, HTTP server, React dashboard, tests, and scheduled refresh scripts.

They give an agent the repository layout, technology choices, commands, and available tools needed to change the service safely.

How sandraschi/glama-status-mcp configures Codex and OpenCode

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/sandraschi/glama-status-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/sandraschi/glama-status-mcp

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/sandraschi/glama-status-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/sandraschi/glama-status-mcp/agents-md)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 629 This file is loaded in full into every session.

When invoked 629 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00252	$0.00252
Sonnet 5.5	$0.00126	$0.00126
Haiku 4.5	$0.00063	$0.00063

Measured 2mo ago against content hash d1d0539533bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

AGENTS.md · 70 lines

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, deltas
glama_scores_summary - Grade distribution + per-repo stats
glama_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 scores
tools - Per-tool TDQS dimension scores
score_snapshots - One row per refresh run
score_history - Denormalized per-repo per-snapshot for fast deltas
refresh_log - Timestamps and errors per refresh
fleet_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

Read the full file on GitHub · 70 lines

Changes

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.

2mo ago First seen · 70 lines · 629 tokens per session scan A d1d0539533bf

Subscribe to this mod's changes

glama-status-mcp AGENTS.md is an instructions file published in the GitHub repository sandraschi/glama-status-mcp (3 stars, last pushed 14d ago), licensed MIT. It adds 629 tokens to every session, about $0.0025 per session on Opus 5.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.

Analytics and metrics Databases LLM dashboard fastmcp fleet glama mcp

glama-status-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
glama-status-mcp AGENTS.mdsandraschi/glama-status-mcp	Instructions file	3	14d ago	MIT	A	629	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

glama-status-mcp: Instructions file for Codex