Every card is plain markdown at a stable, version-pinned URL. Use the security card directly as a developer, or set it up for use by an AI agent.
Find the cards for a library, then wire them into your repo so your assistant reads them automatically.
Browse the catalog or hit ⌘K to search. Each library page lists every category card.
It summarizes the library's secure-by-default posture. Category cards then go deep on one vulnerability class each.
Copy a single card from its page, or download the whole library bundle from /downloads/{language}/{library}/{version}.md.
Add a rule file to your repo so the agent consults the cards whenever it touches that library. Pick your tool below.
Drop one of these into your project. These examples use Asp Net; swap in the library and URL you need.
## Security cards
When writing or reviewing code that uses Asp Net, first read
https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10.md
and apply every "Secure rule" from the categories relevant to the change.# Security cards
Whenever you touch Asp Net code in this repo, fetch the security cards at
https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10.md
and follow every "Secure rule" from the relevant categories. Cards are
version-pinned — match the Asp Net version in the dependency manifest.---
description: Security cards for Asp Net — consult before editing Asp Net code
globs: ["**/*"]
alwaysApply: false
---
When writing or reviewing Asp Net code, first read
https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10.md
and apply every "Secure rule" from the relevant category cards.When writing or reviewing code that uses Asp Net, first read the security
cards at https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10.md and apply every "Secure rule"
from the categories relevant to the change.Every URL is a static file — no API, no auth. Pull exactly the scope you need.
# Learn the recommended workflow
curl https://securitycards.rewarelabs.com/security-cards.md
# Discover every supported library and version
curl https://securitycards.rewarelabs.com/llms.txt
# Just the C# libraries
curl https://securitycards.rewarelabs.com/llms/c%23.txt# Every C# library's cards in one file
curl -O https://securitycards.rewarelabs.com/downloads/c%23.md# Every card for Asp Net v10.0.10
curl -O https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10.md# Just the security blueprint
curl -O https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10/0_security_blueprint.md# Just the Access Control card
curl -O https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10/access-control.mdFetch the narrowest file that covers the task, then apply its rules. Everything is raw markdown at a predictable URL.
GET /security-cards.md for the recommended workflow, then use /llms.txt or a smaller language catalog to discover canonical URLs.
Single card < blueprint < library bundle < language bundle. Token estimates are listed in the catalog — take the smallest that covers the change.
Follow every "Secure rule" in the loaded cards. Cards are version-pinned — match the project's dependency version.
Start with the scenario that matches the task. Each workflow follows the same path: understand the context, fetch only what is needed, apply the rules, and return verifiable sources.
Selecting dependencies, architecture, and secure defaults before implementation begins.
Verify planned versions in /llms.txt, then read each library’s Security Blueprint and relevant bundle.
Turn the rules into architecture decisions and persistent AGENTS.md, CLAUDE.md, or tool-specific instructions.
A security-aware implementation plan that names the chosen versions, applied rules, and canonical sources.
Changing a focused code path with one or more known library dependencies.
Read the exact dependency version from the manifest and load the narrowest matching category card.
Follow every applicable Secure rule while coding, then run the card’s Review checks against the final change.
A completed feature with a concise security summary and the canonical cards that informed it.
Auditing an existing implementation for unsafe library usage and missing controls.
Inventory supported dependencies and versions, then load relevant blueprints and category cards.
Compare real code paths against both Secure rules and Review checks; do not infer findings without evidence.
Prioritized findings with severity, affected code, remediation, and canonical Security Cards sources.
Copy one into your system prompt or hand it to the model directly.
Read https://securitycards.rewarelabs.com/security-cards.md for the recommended Security Cards workflow.
Use https://securitycards.rewarelabs.com/llms.txt to find supported languages, libraries, versions, and canonical URLs.
If you already know the stack is C#, fetch https://securitycards.rewarelabs.com/llms/c%23.txt
instead. Then load the narrowest file that covers the code you're changing.This is a C# codebase. Before writing code, fetch
https://securitycards.rewarelabs.com/downloads/c%23.md and apply every "Secure rule"
that applies to the libraries in use. This file is large — prefer a
per-library file when you know which library you're touching.You are working with Asp Net v10.0.10. Before writing code,
fetch https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10.md and apply every "Secure rule"
from the relevant category cards to your changes.Before touching this Asp Net code, read the security blueprint at
https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10/0_security_blueprint.md for the
secure-by-default posture, then follow it as you write code.You are changing Asp Net v10.0.10 code. Fetch
https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10/access-control.md and apply every
"Secure rule" in the Access Control card.Canonical URL shapes cover everything, from the whole catalog down to a single card.
https://securitycards.rewarelabs.com/security-cards.mdRecommended workflows and scope-selection guidance.https://securitycards.rewarelabs.com/llms.txtEvery language, library, version, and canonical card URL.https://securitycards.rewarelabs.com/llms/c%23.txtJust one language — smaller context.https://securitycards.rewarelabs.com/downloads/c%23.mdEvery library for a language, one file.https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10.mdEvery card for one library/version.https://securitycards.rewarelabs.com/downloads/c%23/asp-net/v10-0-10/access-control.mdOne category. The blueprint is 0_security_blueprint./security-cards.md explains how humans and agents should use the platform./llms.txt is the source of every supported language, library, version, and canonical URL, following the llms.txt convention. Working in one language? Use a smaller map like/llms/c#.txt.