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 causify-ai/helpers --skill readme.explain_codegit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/readme.explain_code)<a href="https://agentmods.dev/skills/causify-ai/helpers/readme.explain_code"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/readme.explain_code/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/causify-ai/helpers/readme.explain_code"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/readme.explain_code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00013 | $0.01634 |
| Opus 5.5 | $0.00005 | $0.00654 |
| Sonnet 5.5 | $0.00003 | $0.00327 |
| Haiku 4.5 | $0.00001 | $0.00163 |
Grade A, and why
readme.explain_code 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Read one or more Python files passed by the user and generate a markdown file
explain_code.<descr>.mdthat documents their classes, functions, interfaces, and relationships
Workflow
Read the Files
- Read every Python file
<FILE>passed by the user or referenced in the request
Generate the Document
- Generate the file in the directory where you are running, named
explain_code.<descr>.md<descr>is a short slug for what was read, typically the source file's basename without extension (e.g.,batch_call_auctionforbatch_call_auction.py); pick a combined slug when documenting several files together
- Include the five sections below, in this exact order
- Under each section, print one level-2 header (
##) per file read, using the same path that was used to read the file in Step 1 (this disambiguates files that share a basename in different directories) - Omit a section, or a file's subsection within it, entirely if there is nothing
to report; never print an empty header or a placeholder bullet like
- - Do not print result to screen but only to file
Verify
- Follow the
# Verificationchecklist below before returning the result
File Description
-
Print a nested bullet list for each file describing what are the abstractions and functionalities the file contains
-
Keep the files ordered in terms of use relationship
- E.g., if file X is imported by Y, then X should come before Y in the list
-
E.g.,
- `batch_call_auction.py` - In-memory order book for a batch call auction - Queues buy/sell orders, buckets by capability tier - Clears each tier at a uniform price once per round - `passthrough_proxy.py` - LLM provider gateway - Routes a prompt to a registered provider - Times the call, estimates cost, and logs every request/response pair for later query
Class Description
- For each file, print one bullet per Python class with a description under 20 words
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 Changed ec2def0b300f
- 1mo ago First seen · 216 lines · 13 tokens per session scan A c8a79b28dbc3
readme.explain_code is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 1,634 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
matlab
Builds, reviews, migrates, and plans MATLAB or GNU Octave numerical workflows. Use for arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
pennylane
Builds and differentiates PennyLane quantum circuits, hybrid PyTorch or JAX models, molecular VQE and QAOA workflows. Use for variational quantum algorithms, quantum machine learning, simulator validation, and moving validated circuits to provider plugins. For hardware-specific compilation use qiskit or cirq; for…
rocm-kernels
Provides guidance for writing and benchmarking optimized Triton kernels for AMD GPUs (MI355X, R9700) on ROCm, targeting HuggingFace diffusers (LTX-Video, SD3, FLUX) and transformers. Core kernels: RMSNorm, RoPE 3D, GEGLU, AdaLN. Includes XCD swizzle, autotune, diffusers integration patterns, and LTX-Video pipeline…
holoscan-install-wheel
Install Holoscan SDK Python wheel via pip into a venv. Use for Python installs; not for native C++/apt or Conda installs.
typing-exclusion-worker
Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured completion summary. Use when running parallel typing-debt workers or when asked to remove modules from pyproject mypy exclusion overrides.
python
Python development with ruff, mypy, pytest - TDD and type safety.