Borrowing it
Nothing to install: this file belongs to smchase/piazza-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/smchase/piazza-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/smchase/piazza-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/smchase/piazza-mcp/claude-md)<a href="https://agentmods.dev/instructions/smchase/piazza-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/smchase/piazza-mcp/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.01250 | $0.01250 |
| Opus 5 | $0.00625 | $0.00625 |
| Sonnet 5 | $0.00250 | $0.00250 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade C, and why
piazza-mcp CLAUDE.md scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. `rm -rf dist && uv build && uv publish` How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Piazza MCP Server — Project Context
What This Is
An MCP server that lets AI agents browse a user's Piazza course forum — searching posts, reading questions/answers, and discovering relevant course content to assist with coursework.
Architecture
src/ layout with uv for dev and running. Two source files:
server.py— FastMCP server with 4 tools, startup auth, class state management, tool descriptionsformatting.py— html2text wrapper, snippet generation, post/answer/followup formatting
Authentication
Env vars: PIAZZA_EMAIL, PIAZZA_PASSWORD. Server calls Piazza.user_login() once on startup.
Design Decisions
Tool Design (4 tools)
list_classes() — Returns only active enrolled classes: name, term, course number, network ID. Filters out old/inactive classes via the status field from Piazza's user.status API. Does not show which class is currently active in the server — the agent always treats it as a fresh start and must select a class. This ensures the agent always follows the same predictable flow: list → select → search.
set_class(network_id) — Sets the active class and returns class name/term (confirmation) plus list of all available folders/tags. Called once at the start of a session before any searching. The agent doesn't know whether a class is already active, so it always calls this — which is the desired behavior.
Folder names matter because naming isn't predictable — "assignment 1" might be "hw1", "a1", or "problem_set_1". The agent needs to see the actual folder names to map user intent to the right filter.
search_posts(query, folder, limit) — Unified search/browse tool. Three modes:
- No args: recent posts (feed/browse mode)
- query only: keyword search across all posts
- folder only: all posts in a specific folder
- both: keyword search filtered to a folder (search API → client-side folder filter)
Returns per result: post number (@123), subject, snippet (~150 chars), folders/tags, answer status (instructor/student/unanswered), type, date.
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.
- 6d ago First seen · 96 lines · 1,250 tokens per session scan C 008304f06bc4
piazza-mcp CLAUDE.md is an instructions file published in the GitHub repository smchase/piazza-mcp (4 stars, last pushed 7mo ago), licensed MIT. It adds 1,250 tokens to every session, about $0.0063 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.