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 iblai/government-agents --skill granicus-govdeliverygit clone --depth 1 https://github.com/iblai/government-agentsWrote 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/iblai/government-agents/granicus-govdelivery)<a href="https://agentmods.dev/skills/iblai/government-agents/granicus-govdelivery"><img src="https://agentmods.dev/badge/skills/iblai/government-agents/granicus-govdelivery/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/iblai/government-agents/granicus-govdelivery"><img src="https://agentmods.dev/badge/skills/iblai/government-agents/granicus-govdelivery.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.00031 | $0.00577 |
| Opus 5 | $0.00015 | $0.00289 |
| Sonnet 5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
granicus-govdelivery 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Granicus / GovDelivery
What it is
Granicus (formerly GovDelivery) is the leading digital communications platform purpose-built for government agencies. It manages subscriber lists, sends email and SMS bulletins to opted-in constituents, and provides engagement analytics. Used by thousands of federal, state, and local agencies to deliver service notifications, emergency updates, and public information campaigns.
When to use this skill
- Drafting and scheduling email or SMS bulletins to subscriber lists on a specific topic
- Sending immediate notifications for service disruptions, emergency updates, or deadline reminders
- Looking up subscriber counts, topic subscriptions, and list growth metrics
- Retrieving delivery analytics (open rates, click-through rates, bounces, unsubscribes) for a recent bulletin
- Managing topic subscriptions and public subscribe page configurations
Credentials
This skill authenticates using variables from the OpenClaw daemon env file ~/.openclaw/.env (template: .env.example). Required variables:
GRANICUS_API_BASE_URL- agency Granicus API base URL (e.g.,https://api.govdelivery.com)GRANICUS_API_TOKEN- bearer token issued from the Granicus admin console
Key operations
GET /api/account/bulletins— list recent bulletins with status and send datesPOST /api/account/bulletins— create a new email or SMS bulletin draftPOST /api/account/bulletins/{id}/publish— publish/send a draft bulletin immediatelyPOST /api/account/bulletins/{id}/schedule— schedule a bulletin for future deliveryGET /api/account/topics— list subscriber topics with counts and category assignmentsGET /api/account/bulletins/{id}/stats— retrieve open rate, CTR, bounce, and unsubscribe countsGET /api/account/subscribers— look up subscriber record by email address
Notes
- Bulletins sent via the API bypass the CMS workflow approval step; agencies should implement a supervisor approval gate before calling the publish endpoint.
- SMS messages are subject to TCPA regulations and carrier delivery rate limits; confirm opt-in compliance with the agency legal counsel.
- The API uses account-scoped authentication; each Granicus account corresponds to one agency or sub-agency deployment.
- Rate limit: not publicly documented; follow exponential back-off on 429 responses and avoid bulk send loops.
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 · 38 lines · 31 tokens per session scan A 4e17f071f5ea
granicus-govdelivery is a skill published in the GitHub repository iblai/government-agents (10 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 577 once invoked, about $0.0002 per session on Opus 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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.