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/causify-ai/helpers/auto_task.create_specsnpx skills add causify-ai/helpers --skill auto_task.create_specsgit clone --depth 1 https://github.com/causify-ai/helpersWhat 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.00007 | $0.00668 |
| Opus 5 | $0.00003 | $0.00334 |
| Sonnet 5 | $0.00001 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
auto_task.create_specs 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Given a list of TODOs provided by the user in the form
<FILE>:<LINE_NUM>:<TODO description> ./helpers/hmarkdown_coloring.py:235:def colorize_bullet_points_in_slide(
Workflow
Step 1
- Read each TODO and understand the problem
- If it's a bug:
- Make sure to understand the root cause
- Run experiments to verify that you understood the issue and its root cause
- Devise a plan to fix the problem
- Devise a plan to verify that the problem is fixed
Step 2
- Create a plan
plan.todo_janitor.mdfor fixing the tests using the template below:## [ ] Issue<num>: <short description of the issue> ### Info - **Original description**: <FILE>:<LINE_NUM>:<TODO description> ### Proposed fix - **Type**: [feature|bug|improvement|cosmetic] - **Reason of the problem**: ... - **Proposed fix**: ... - ... - **Confidence in the fix**: [low|medium|high] - **Fix complexity**: [low|medium|high] - **Verification plan**: - <How to verify that the problem is fixed> ### Status - **Status**: [proposed|approved|issue_filed|working|PR_ready|merged] - **GitHub issue title**: ... - **GitHub issue link**: ... - **PR link**: ... - **Git worktree**: ... # [ ] 2: ... ... - Write the comments as bullet points according to
.claude/skills/markdown.rules.mdand.claude/skills/text.rules.mdwith minimal text - Do not make any change to the code, but only propose the fixes
Follow the Conventions
- When writing code, follow instructions in
.claude/skills/coding.rules.md- Refer to skills in
.claude/skills/coding.*/SKILL.mdto follow the repo best practices
- Refer to skills in
- For bugs:
- Add unit tests to check that the problem was present and then it's fixed (red/green approach)
- Follow instructions in
.claude/skills/testing.rules.md - Refer to skills in
.claude/skills/testing.*/SKILL.mdto follow the repo best practices
- For renaming, make sure the entire code base is checked to make sure everything
is updated
- Follow
.claude/skills/coding.rename/SKILL.md
- Follow
- For change of function signature, make sure all the calling instances have been updated
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 · 80 lines · 7 tokens per session scan A e32ecfac8896
auto_task.create_specs is a skill published in the GitHub repository causify-ai/helpers (145 stars, last pushed 2d ago), licensed Apache-2.0. It adds 7 tokens to every session and 668 once invoked, about $0.0000 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.