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 commands/secondsky/claude-skills/r2-cors-debuggit clone --depth 1 https://github.com/secondsky/claude-skillsWrote 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/commands/secondsky/claude-skills/r2-cors-debug)<a href="https://agentmods.dev/commands/secondsky/claude-skills/r2-cors-debug"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/r2-cors-debug.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.00016 | $0.01105 |
| Opus 5 | $0.00008 | $0.00553 |
| Sonnet 5 | $0.00003 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
cloudflare-r2:cors-debug scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **Provides curl test commands** to verify setup How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
R2 CORS Debugger
Systematically diagnose and fix CORS (Cross-Origin Resource Sharing) configuration issues for R2 buckets.
Required Information
- Bucket name:
{{bucket_name}} - Origin domain (e.g., https://example.com):
{{origin}} - Methods needed (e.g., GET, PUT, POST, DELETE):
{{methods}} - Error message (from browser console, if any):
{{error_message}}
What This Command Does
- Checks current CORS policy on bucket
- Generates correct CORS configuration for your use case
- Provides curl test commands to verify setup
- Shows Dashboard configuration steps
- Explains common CORS pitfalls
Common CORS Errors
| Error Message | Cause | Fix |
|---|---|---|
| "No 'Access-Control-Allow-Origin' header" | Missing origin in AllowedOrigins | Add your domain |
| "Method PUT is not allowed" | Method not in AllowedMethods | Add PUT to allowed methods |
| "Header 'Content-Type' not allowed" | Header not in AllowedHeaders | Add Content-Type |
| "Credentials mode requires specific origin" | Using wildcard with credentials | Use specific origin |
CORS Configuration Template
[
{
"AllowedOrigins": [
"https://example.com",
"https://www.example.com"
],
"AllowedMethods": [
"GET",
"PUT",
"POST",
"DELETE"
],
"AllowedHeaders": [
"Content-Type",
"Authorization",
"X-Requested-With"
],
"ExposeHeaders": [
"ETag",
"Content-Length"
],
"MaxAgeSeconds": 3600
}
]
Dashboard Configuration Steps
- Navigate to R2 → Select your bucket
- Click Settings tab
- Scroll to CORS Policy section
- Click Edit CORS policy
- Paste JSON configuration
- Click Save
Testing CORS with curl
# Test preflight request (OPTIONS)
curl -v \
-H "Origin: https://example.com" \
-H "Access-Control-Request-Method: PUT" \
-H "Access-Control-Request-Headers: Content-Type" \
-X OPTIONS \
"https://{{bucket_name}}.{{account_id}}.r2.cloudflarestorage.com/test.txt"
# Expected response headers:
# Access-Control-Allow-Origin: https://example.com
# Access-Control-Allow-Methods: GET, PUT, POST, DELETE
# Access-Control-Allow-Headers: Content-Type
# Access-Control-Max-Age: 3600
# Test actual request (PUT)
curl -v \
-H "Origin: https://example.com" \
-H "Content-Type: text/plain" \
-X PUT \
"https://{{bucket_name}}.{{account_id}}.r2.cloudflarestorage.com/test.txt" \
-d "Test data"
# Expected response headers:
# Access-Control-Allow-Origin: https://example.com
# Access-Control-Expose-Headers: ETag
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 · 157 lines · 16 tokens per session scan A cd380a4d560b
cloudflare-r2:cors-debug is a command published in the GitHub repository secondsky/claude-skills (214 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 1,105 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
correlate
Find related failures through pattern matching.
diff
Compare two command outputs with intelligent diff.
open
Open/retrieve an offloaded output by ID or shortcut.
search
Search through offloaded outputs with hard caps.
stats
Show FewWord session statistics with rich output and token savings.
timeline
Visual timeline of command outputs in current session.