Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/washingtonwei/project-pulse/claude-mdgit clone --depth 1 https://github.com/Washingtonwei/project-pulseWrote 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/washingtonwei/project-pulse/claude-md)<a href="https://agentmods.dev/instructions/washingtonwei/project-pulse/claude-md"><img src="https://agentmods.dev/badge/instructions/washingtonwei/project-pulse/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 | $0.02679 | $0.02679 |
| Opus 5 | $0.01340 | $0.01340 |
| Sonnet 5 | $0.00536 | $0.00536 |
| Haiku 4.5 | $0.00268 | $0.00268 |
Grade A, and why
project-pulse 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 4d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Project Pulse is a web application for managing senior design / capstone course projects. Students submit weekly activity reports and peer evaluations; instructors monitor progress via dashboards. It also includes a Requirements Authoring & Management (RAM) module that lets student teams define software requirements before coding — project glossary, vision and scope, use cases, business rules, software requirements specifications, and traceability.
RAM functionality is built spec-first: its requirements live as Markdown under docs/requirements/ and drive implementation through the /design → /implement workflow. See Spec-driven development below before adding or changing RAM features.
The overarching development methodology these workflows instantiate — spec-driven and agent-assisted, with a breadth-complete, depth-shallow architecture validated by a thin vertical slice before fanning out per use case — is written up in docs/methodology.md.
Starting the Project
All three services must be running for local development. Run them in this order:
- Docker services (MySQL on 3306, Mailpit SMTP on 1025 / web UI on 8025):
docker-compose up -d - Backend (Spring Boot on port 80, dev profile with seed data):
cd backend mvnw.cmd spring-boot:run # Windows ./mvnw spring-boot:run # macOS/Linux - Frontend (Vite dev server on http://localhost:5173):
cd frontend npm install npm run dev
The app is ready at http://localhost:5173. Mailpit UI is at http://localhost:8025.
Stopping the Project
- Backend & Frontend: Kill processes by port to avoid affecting other Java/Node processes:
# Windows (PowerShell) — backend on port 80, frontend on port 5173 (Get-NetTCPConnection -LocalPort 80 -ErrorAction SilentlyContinue).OwningProcess | ForEach-Object { Stop-Process -Id $_ -Force } (Get-NetTCPConnection -LocalPort 5173 -ErrorAction SilentlyContinue).OwningProcess | ForEach-Object { Stop-Process -Id $_ -Force } # macOS/Linux lsof -ti:80 | xargs kill lsof -ti:5173 | xargs kill - Docker services:
docker-compose down
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.
- 4d ago First seen · 139 lines · 2,679 tokens per session scan A 5d5115b7b92b
project-pulse CLAUDE.md is an instructions file published in the GitHub repository Washingtonwei/project-pulse (2 stars, last pushed today), licensed Apache-2.0. It adds 2,679 tokens to every session, about $0.0134 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
bsu-tool CLAUDE.md
Instructions for bsu-tool/bsu-tool, covering claude.md — bsu-tool project context, what this project is, core workflow, language and toolchain and repository structure.
flyrank-capstone-social-studio AGENTS.md
AGENTS.md instructions for Sudeozubek/flyrank-capstone-social-studio: Do not rely on Lovable Cloud DB credentials in .env.
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).
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.
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.
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.