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 skills add authzed/authzed-marketplace --skill authorization-testinggit 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/skills/authzed/authzed-marketplace/authorization-testing)<a href="https://agentmods.dev/skills/authzed/authzed-marketplace/authorization-testing"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/authorization-testing/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/skills/authzed/authzed-marketplace/authorization-testing"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/authorization-testing.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.00041 | $0.01068 |
| Opus 5.5 | $0.00016 | $0.00427 |
| Sonnet 5.5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
Authorization Testing 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authorization Testing
This skill provides guidance on testing SpiceDB-based authorization systems, including test data fixture generation, test scenario design, and integration testing patterns.
Overview
Testing authorization requires:
- Test fixtures: Relationship data representing test scenarios
- Test scenarios: Expected permission outcomes
- Integration tests: End-to-end authorization flows
- Negative tests: Verify denials work correctly
Good authorization tests cover both positive cases (access granted) and negative cases (access denied), and test edge cases like hierarchical inheritance and complex permission rules.
Quick Reference
| Need to... | Read This |
|---|---|
| Find test scenario patterns | references/test-patterns.md |
| Generate fixture data | references/fixture-generators.md |
| See a complete Go test suite | examples/go_test.go |
| See SpiceDB assertion tests | examples/assertions.yaml |
| See load/perf testing | examples/load_test.py |
Test Fixture Generation
Fixtures establish the relationship graph for testing. Organize by scenario, using your schema's actual definition and relation names (not generic placeholders).
See references/fixture-generators.md for fixture structure patterns and helper
functions in Go, Python, and TypeScript.
Use /spicedb-dev:test-permissions to generate fixtures directly from a schema.
Test Scenarios
See references/test-patterns.md for the complete scenario library with 14 patterns covering:
direct access, role-based access, hierarchical inheritance, sharing (wildcard and domain),
complex multi-path, revocation, edge cases, caveated permissions, and CI integration patterns.
Integration Testing
Integration tests verify authorization in the context of your application.
Pattern: Setup, execute, verify, cleanup.
See examples/go_test.go for a complete Go test suite demonstrating:
- Client setup with
serve-testingisolation (unique token per test) - Schema loading, relationship writing, and permission checking helpers
- Table-driven positive and negative test cases
- Revocation testing
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 122 lines · 41 tokens per session scan A 9e4eec3326ec
Authorization Testing is a skill published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,068 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.