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 agents/pixeltable/pixeltable-skill/pixeltable-debuggergit clone --depth 1 https://github.com/pixeltable/pixeltable-skillWhat 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.00056 | $0.00267 |
| Opus 5 | $0.00028 | $0.00133 |
| Sonnet 5 | $0.00011 | $0.00053 |
| Haiku 4.5 | $0.00006 | $0.00027 |
Grade A, and why
pixeltable-debugger 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 today.
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
You are a Pixeltable debugging specialist. Follow the skill's references.
- Read the
pixeltableskill critical warnings and anti-patterns.md. - Inspect with CLI first:
pxt describe,pxt errors,pxt status. See cli.md. - Then SDK:
t.describe(), targetedcollect(),<col>_errortype/<col>_errormsg, andt.recompute_columns()after fixing the cause (re-insert does not recompute existing rows). - For config/rate limits: core-api.md.
Always report: root cause, the exact minimal fix, and a verification command (pxt errors, recompute_columns, re-collect()).
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.
- today Changed · -3 tokens per session 1c1a89ac479e
- 3d ago First seen · 14 lines · 59 tokens per session scan A 0713a6ac19a8
pixeltable-debugger is an agent published in the GitHub repository pixeltable/pixeltable-skill (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 267 once invoked, about $0.0003 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-30.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
streaming
Stream responses from AI providers in real-time using callbacks that execute at different points in the streaming lifecycle.
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
mlops-reviewer
MLOps / model lifecycle pre-implementation reviewer. Specialises in dataset versioning (DVC / LakeFS), distributed training cost budgets, model registry (MLflow / W&B), drift detection (Evidently / WhyLabs), bias / fairness audit (Fairlearn / AIF360), shadow + A/B model serving, and EU AI Act high-risk classification.…
by-epitope
Deep epitope analysis agent. Maps binding interfaces from PDB structures, classifies epitope type, assesses druggability, identifies cryptic sites, cross-references SAbDab, and generates hotspot arrays in BoltzGen entities YAML format.
prompt_engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…