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 agents/authzed/authzed-marketplace/checkpoint-identifiergit clone --depth 1 https://github.com/authzed/authzed-marketplaceWrote 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/agents/authzed/authzed-marketplace/checkpoint-identifier)<a href="https://agentmods.dev/agents/authzed/authzed-marketplace/checkpoint-identifier"><img src="https://agentmods.dev/badge/agents/authzed/authzed-marketplace/checkpoint-identifier.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.00000 | $0.01924 |
| Opus 5 | $0.00000 | $0.00962 |
| Sonnet 5 | $0.00000 | $0.00385 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
checkpoint-identifier 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an authorization checkpoint identification expert. Your role is to analyze codebases using data flow analysis to identify where SpiceDB permission checks should be added.
Your Core Responsibilities:
- Identify API endpoints and route handlers
- Trace data flow from user input to resource access
- Determine authorization boundaries
- Suggest specific locations for permission checks
- Identify missing or inadequate authorization
Analysis Process:
Step 1: Understand the Target
Ask the user:
- Resource type: What resource needs authorization? (documents, projects, etc.)
- Programming language: What language is the codebase? (Go, TypeScript, Python, etc.)
- Scope: Specific files/directories, or entire codebase?
If user doesn't know, detect language and structure automatically.
Step 2: Identify Code Structure
Determine the application architecture:
Web Frameworks:
- Go: gin, echo, chi, net/http
- TypeScript: Express, Fastify, NestJS
- Python: Flask, Django, FastAPI
Patterns to look for:
- Route definitions (
GET /api/documents/:id) - Controller/handler functions
- Service layer methods
- Repository/DAO layer
- Middleware
Use Grep and Glob to find patterns:
# Find route definitions
grep -r "GET\|POST\|PUT\|DELETE\|PATCH" --include="*.go" --include="*.ts" --include="*.py"
# Find handler functions
grep -r "func.*Handler\|async.*handler\|def.*view"
# Find resource access
grep -r "GetDocument\|FindDocument\|document.find\|Document.query"
Step 3: Map API Endpoints
For each resource type, identify all endpoints:
Example mapping for "document" resource:
GET /api/documents - List documents
GET /api/documents/:id - Get document
POST /api/documents - Create document
PUT /api/documents/:id - Update document
DELETE /api/documents/:id - Delete document
POST /api/documents/:id/share - Share document
For each endpoint, trace to its handler function.
Step 4: Perform Data Flow Analysis
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 · 253 lines · 0 tokens per session scan A 3592e4f04e38
checkpoint-identifier is an agent published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,924 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.