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 brandhaug/b2b-saas-starter --skill configure-cloudflare-monitoringgit clone --depth 1 https://github.com/brandhaug/b2b-saas-starterWrote 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/brandhaug/b2b-saas-starter/configure-cloudflare-monitoring)<a href="https://agentmods.dev/skills/brandhaug/b2b-saas-starter/configure-cloudflare-monitoring"><img src="https://agentmods.dev/badge/skills/brandhaug/b2b-saas-starter/configure-cloudflare-monitoring/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/brandhaug/b2b-saas-starter/configure-cloudflare-monitoring"><img src="https://agentmods.dev/badge/skills/brandhaug/b2b-saas-starter/configure-cloudflare-monitoring.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.00052 | $0.00581 |
| Opus 5.5 | $0.00021 | $0.00232 |
| Sonnet 5.5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
configure-cloudflare-monitoring 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 12d 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.
What it actually says
Configure Cloudflare monitoring
Use the existing events and policies in monitoring. Read operations for ownership and independent monitors, and logger policy before handling telemetry. Setup never requires duplicate application events.
- Establish the requested scenario: initial setup, reconcile drift, add a signal,
or verify a deployment. Identify the account, stage, deployed Worker names and
versions, operator, and existing dashboard/rule IDs from the private operations
record. Derive names from
stageResourceNamesininfra/bindings.tsand verify them against the deployment. Scope every chart and rule to that stage. - Read setup to discover actual datasets and fields, choose supported declarative resources or the dashboard, and prepare the configuration. Reuse available access; Worker deployment permission does not prove telemetry query or alert-edit permission. A 403 is an access gap, not an empty dataset.
- Reconcile only the requested resources by their recorded IDs. Present the concrete changes before applying them. Existing authorization for setup covers those changes; ask only for missing scope or authorization. Sending a test or enabling delivery requires an explicitly identified, authorized destination. Never infer recipients from Git, account profiles, or existing unrelated rules. Agent connections require their own explicit request.
- Run the relevant verification scenarios. Report each result as local, live verified, blocked, or unsupported. Read back saved configuration, then repeat reconciliation and show that no duplicate resource or unnecessary change results. Provider acceptance alone does not prove delivery.
- Record IDs, exact queries or chart settings, discovered field mappings, UTC windows, sanitized aggregates and remaining checks in the private operations record. Keep raw logs, credentials, recipient addresses and secret webhook URLs out of repository artifacts. If live access is missing, finish the configuration plan and local checks first, then request the exact account/stage, access route, or destination needed. Do not describe a prepared plan as deployed monitoring.
For a new signal, first locate its canonical event and owning capability. Apply the same discovery, freshness, recovery, and rerun checks; change application telemetry only when the requested scenario lacks evidence. For incident diagnosis, use investigate-cloudflare.
What ships with it
2 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.
- 12d ago First seen · 43 lines · 52 tokens per session scan A be076cc77e23
configure-cloudflare-monitoring is a skill published in the GitHub repository brandhaug/b2b-saas-starter (51 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 581 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-10-04.
Other skills, from other repositories
add-a-service
Scaffold a new service under services/ in the builders-stack monorepo. Use when something needs its own URL, port, or independent deploy. Covers the package, entrypoint, config, Tilt, deployment registry, and shared small-image build path.
add-a-lib
Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…
apps-deploying-vercel-branches
Shared deployment procedure for the -deployer agent family — force-pushing an environment branch that Vercel (or a GitHub Actions workflow) builds from. Covers three patterns (direct force-push, scheduled staging workflow, scheduled test-only workflow) plus the shared Vercel MCP post-deploy verification protocol. Use…
turborepo
Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
adapter-aws-lambda
Deploy tRPC on AWS Lambda with awsLambdaRequestHandler() from @trpc/server/adapters/aws-lambda for API Gateway v1 (REST, APIGatewayProxyEvent) and v2 (HTTP, APIGatewayProxyEventV2), and Lambda Function URLs. Enable response streaming with awsLambdaStreamingRequestHandler() wrapped in awslambda.streamifyResponse().…
adapter-fetch
Deploy tRPC on WinterCG-compliant edge runtimes with fetchRequestHandler() from @trpc/server/adapters/fetch. Supports Cloudflare Workers, Deno Deploy, Vercel Edge Runtime, Astro, Remix, SolidStart. FetchCreateContextFnOptions provides req (Request) and resHeaders (Headers) for context creation. The endpoint option…