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.
git clone --depth 1 https://github.com/ctxs-ai/ctxs.aiWrote 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/rules/ctxs-ai/ctxs.ai/astro-site)<a href="https://agentmods.dev/rules/ctxs-ai/ctxs.ai/astro-site"><img src="https://agentmods.dev/badge/rules/ctxs-ai/ctxs.ai/astro-site/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.
<a href="https://agentmods.dev/rules/ctxs-ai/ctxs.ai/astro-site"><img src="https://agentmods.dev/badge/rules/ctxs-ai/ctxs.ai/astro-site.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00520 |
| Opus 5.5 | $0.00000 | $0.00208 |
| Sonnet 5.5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
astro-site 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctxs.ai Site/Frontend
This part of the project implements the web interface for ctxs.ai using Astro with React components and Tailwind CSS for styling.
Architecture Overview
The site follows Astro's file-based routing system with these key directories:
site/src/pages/: Contains route definitions and page componentssite/src/components/: Reusable UI components (both Astro and React)site/src/layouts/: Page layouts and templatessite/src/lib/: Utility functions and helperssite/src/styles/: Global styles and Tailwind configuration
Technology Stack
- Framework: Astro - A modern static site builder with island architecture
- UI Components: React 19 (with JSX/TSX)
- Styling: Tailwind CSS 4 with custom components using shadcn/ui architecture
- Deployment: Cloudflare Pages (configured with Astro Cloudflare adapter)
Development Patterns
Component Guidelines
- Prefer Astro components (
.astro) for static UI elements and page layouts - Use React components (
.tsx) for interactive elements that require client-side JavaScript - Follow the component structure in
site/src/components/ui/for consistent styling
API endpoints
- Add
export const prerender = falseto the beginning of API endpoints so that they are deployed as server functions
Styling Approach
- Use Tailwind utility classes for styling
- UI components follow the shadcn/ui pattern for consistency and maintainability
- Custom styles should be added to the appropriate files in
site/src/styles/
Data Fetching
- The site interfaces with the context system to display markdown files
- API routes are defined in
site/src/pages/api/ - Context data is fetched and rendered through the components in
site/src/components/
Best Practices
- Use TypeScript for type safety and better developer experience
- Keep components small and focused on a single responsibility
- Follow Astro's performance patterns by minimizing client-side JavaScript
- Maintain accessibility standards in all UI components
- Use the existing UI component library rather than creating custom styles
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.
- 1mo ago First seen · 59 lines · 0 tokens per session scan A f8ff72f46ea4
astro-site is a cursor rule published in the GitHub repository ctxs-ai/ctxs.ai (26 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 tokens. 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
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
ui-assets
Docker staging for symlinked SPA and documentation assets.
performance-optimization
A guide to improving the speed and responsiveness of frontend applications.
design
All tasks related to updating frontend components, CSS, and general styling.
templates
Tera template variables, blocks, and theme conventions.
token-the-ripper
Strip scaffolding. Keep signal.