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 rules/thematters/matters-web/project-structuregit clone --depth 1 https://github.com/thematters/matters-webWhat 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.00375 | $0.00375 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
project-structure 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 2d 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.
What it actually says
Project Structure
Matters Web is a Next.js application that serves as the frontend for Matters.town, a decentralized content publishing platform.
Main Directories
src/components/: Reusable UI components organized by functionalitysrc/pages/: Contains Next.js pages that define application routessrc/views/: Page-level components used by the pages directorysrc/common/: Shared utilities, constants, styles, and helperssrc/gql/: TypeScript types for GraphQL queries and mutations that generated based on GraphQL schema bygen:typecommandsrc/definitions/: TypeScript type definitionssrc/stories/: Contains Storybook stories for component development and testing.public/: Static assets including images, icons, and other resources
Icons
We use SVGR to transform SVGs into React components. For reusability and bundle optimization:
To add a new icon to the project:
- Export 24x24px icon from Figma to
public/static/icons/24px - If the icon color isn't static, replace the values of
fillandstrokeattributes withcurrentColor, and addfill="none"to<svg>
Key Files
- src/pages/_app.tsx: Main application entry point that wraps all pages
- src/pages/_document.tsx: Custom document for controlling the initial HTML
- next.config.js: Next.js configuration
- package.json: Project dependencies and scripts
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.
- 2d ago First seen · 36 lines · 375 tokens per session scan A b12aa21826a4
project-structure is a cursor rule published in the GitHub repository thematters/matters-web (86 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 375 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
tutorial-system-guide
This guide documents the complete tutorial infrastructure in Windmill's frontend, enabling developers to create new interactive tutorials without re-exploring the codebase.
windmill-overview
Windmill is an open-source developer platform for building internal tools, API integrations, background jobs, workflows, and user interfaces. It offers a unified system where scripts are automatically turned into sharable UIs and can be composed into flows or embedded in custom applications.
api-arena-project-progress
Estado actual del proyecto API Arena - servicios implementados, lo que falta, y arquitectura.
api-arena-project-spec
Plataforma educativa competitiva donde estudiantes compiten creando APIs. Evaluación automática mediante tests funcionales, rendimiento, diseño REST y review IA. Incluye Replay system y Multiplayer mode.
api-arena-no-volume-recreation
CRÍTICO — entorno de PRODUCCIÓN. Nunca recrear/borrar volúmenes Docker. Los cambios de BD se aplican SIEMPRE con migraciones idempotentes en caliente.
api-arena-commit-workflow
Commits pequeños y frecuentes, uno por feature/fix cuando funcione y esté verificado.