Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MalekYala/yala-agentic-toolkitnpx agentmods add skills/malekyala/yala-agentic-toolkit/yala-toolkitWrote 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/malekyala/yala-agentic-toolkit/yala-toolkit)<a href="https://agentmods.dev/skills/malekyala/yala-agentic-toolkit/yala-toolkit"><img src="https://agentmods.dev/badge/skills/malekyala/yala-agentic-toolkit/yala-toolkit/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/malekyala/yala-agentic-toolkit/yala-toolkit"><img src="https://agentmods.dev/badge/skills/malekyala/yala-agentic-toolkit/yala-toolkit.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.00125 | $0.01043 |
| Opus 5 | $0.00063 | $0.00522 |
| Sonnet 5 | $0.00025 | $0.00209 |
| Haiku 4.5 | $0.00013 | $0.00104 |
Grade A, and why
yala-toolkit 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 8d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Yala Toolkit
A library of 570 single-file CLI tools. Each is standalone (no cross-imports),
argparse-driven, mostly stdlib-only, and safe to inspect: every tool honors
--help with no side effects. Before writing a throwaway script, check
whether a tool already exists.
All paths below are relative to the toolkit repo root (this skill lives at
.claude/skills/yala-toolkit/ inside it). Use the repo's .venv/bin/python
when it exists; plain python3 otherwise.
Workflow: find → inspect → run
# 1. FIND by keyword (searches names + descriptions, ranked)
yala find "webhook replay" # or: .venv/bin/yala find ...
# 2. INSPECT — summary + full docstring with examples
yala info webhooks webhook-replay
# (equivalently: python src/webhooks/webhook_replay.py --help)
# 3. RUN — args after `--` go to the tool untouched
yala run webhooks webhook-replay -- --file dump.ndjson --target http://127.0.0.1:8080
If the yala entry point isn't installed, run tools directly:
python src/<category>/<tool>.py ... — identical behavior.
Programmatic discovery
tools/data/manifest.json describes every tool:
{name, category, path, description, mutates, json_output, command, examples}.
# tools that write/change things vs read-only
python3 -c "import json;[print(t['path']) for t in json.load(open('tools/data/manifest.json'))['tools'] if t['mutates']]"
mutates: false→ safe to run for information gathering.json_output: true→ supports--jsonfor machine-readable output.yala listshows all categories; eachsrc/<category>/README.mdhas per-tool prose and setup notes.
Conventions that hold across all tools
- Exit codes are gates: checkers/monitors exit non-zero on a finding
(lag too high, cert expiring, new debt, gate BLOCK) so they compose with
CI, cron, and
&&chains. - Flags over config files; where state is needed it's an explicit
--state-dir(never hidden in $HOME). - Network tools default to 127.0.0.1 targets; nothing phones home.
- Missing optional deps fail with a clear install hint — try the tool first rather than pre-installing.
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.
- 8d ago First seen · 87 lines · 125 tokens per session scan A 3c04146bd54e
yala-toolkit is a skill published in the GitHub repository MalekYala/yala-agentic-toolkit (0 stars, last pushed 19d ago), licensed MIT. It adds 125 tokens to every session and 1,043 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…