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 skills/cel-expr/skills/cel-doc-generatornpx skills add cel-expr/skills --skill cel-doc-generatorgit clone --depth 1 https://github.com/cel-expr/skillsWhat 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.00042 | $0.03033 |
| Opus 5 | $0.00021 | $0.01517 |
| Sonnet 5 | $0.00008 | $0.00607 |
| Haiku 4.5 | $0.00004 | $0.00303 |
Grade A, and why
cel-lib-doc-generator 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 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.
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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CEL Library Documentation Generator Skill
Use this skill to inspect CEL (Common Expression Language) extension libraries in Go, C++, or Java and generate or update a comprehensive README.md written from the perspective of that specific language implementation, matching the canonical format established in third_party/cel/go/ext/README.md.
1. Overview & Documentation Colocation Rules
Each CEL repository (cel-go, cel-cpp, cel-java) maintains extension documentation tailored to its language runtime.
Colocation Rule
- Subpackage Documentation: If a library is implemented in its own subpackage or subdirectory (e.g.,
cel-go/ext,cel-go/ext/security/hmac,cel-cpp/extensions,cel-java/extensions), the documentation MUST be colocated directly in that subpackage's directory (e.g.,ext/README.md,ext/security/hmac/README.md,extensions/README.md). - Root Package Documentation: The top-level
ext/README.mdis reserved strictly for extension functions declared directly in the rootext/directory (e.g.,ext/math.go,ext/strings.go,ext/encoders.go).
A colocated library README.md documents:
- Enablement: How to configure and register the extension using that language's environment or compiler builder API.
- CEL Declarations: The functions, overloads, macros, and native types exposed by the library.
- Signatures & Semantics: The standard CEL type signatures, parameter constraints, and edge-case behavior.
- Verified Examples: Concrete CEL expressions extracted directly from unit test suites with their expected return values and error conditions.
2. End-to-End Workflow
Follow this workflow when pointed at a library directory or source package:
flowchart TD
A[Identify Target Language & Subpackage Path] --> B[Execute Language-Specific Symbol Extraction]
B --> C[Extract Verified Examples & Error Cases from Tests]
C --> D[Synthesize Colocated README.md Using doc_template.md]
D --> E[Validate Snippets via Environment Config & CEL Evaluation]
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.
- 2d ago First seen · 239 lines · 42 tokens per session scan A 9b6476155716
cel-lib-doc-generator is a skill published in the GitHub repository cel-expr/skills (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 42 tokens to every session and 3,033 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
pipefy-ai-agents
Use this skill when the user wants to create, read, update, delete, or troubleshoot AI agents (conversational agents with behaviors). Covers 7 MCP tools including pre-flight validation, plus pipe-scoped knowledge bases (list, plain text/document/data lookup CRUD, access probe) attached via dataSourceIds. For…
pipefy-automations
Use this skill when the user wants to create, read, update, or delete traditional automations (if/then rules) or AI automations (prompt-driven). Covers 16 MCP tools. For AI agents (conversational), see skills/ai-agents/.
pipefy-portal-setup
Use this skill when the user wants to list, create, or configure Pipefy portals (main hub, pages, page elements, sub-portals, publish/unpublish). Covers 20 MCP tools on Interfaces + internalapi. Not for pipes/cards.
pipefy-ipaas
Use when the user wants to build, test, publish, or manage iPaaS (Advanced Automations) flows: multi-step integrations with external apps (Slack, Gmail, Google Sheets), incoming webhooks, schedules, routers, code steps, or iPaaS data tables. MCP-only, driven through 4 meta-tools over a per-pipe catalog discovered at…
pipefy-api-fallback
Use this skill when an MCP tool fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier…
pipefy-attachments
Use this skill when the user wants to upload a file to a Pipefy card or table-record attachment field. Covers both input modes — a local filepath and a downloaded fileurl — plus a presigned-URL handshake for uploading a file the server can't read, through the MCP tools and the CLI.