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/coding.reorg_functionsnpx skills add causify-ai/helpers --skill coding.reorg_functionsgit 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.00009 | $0.00366 |
| Opus 5 | $0.00005 | $0.00183 |
| Sonnet 5 | $0.00002 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
coding.reorg_functions 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.
What it actually says
Reorganize Python Functions Within a File
-
Reorganize the Python functions in the user-provided file according to the general rules in the
coding.rules.mdfile for organizing code- Follow the section
## Organize Functions Into Logical Layersfrom the file.claude/skills/coding.rules.md - Follow the section
## Order Layers by Abstraction Levelfrom the file.claude/skills/coding.rules.md - Follow the section
## Order Functions Within Each Layerfrom the file.claude/skills/coding.rules.md - Follow the section
## Keep Related Functions Togetherfrom the file.claude/skills/coding.rules.md - Follow the section
## Mark Private Functionsfrom the file.claude/skills/coding.rules.md
- Follow the section
Additional Guidance
- Avoid circular ordering where possible
- Preserve existing comments and docstrings
- Keep public entry points easy to locate near the end of the file
- Prefer cohesion and readability over strict categorization
Constraints
Preserve Behavior Exactly
- Do not modify functionality, logic, signatures, control flow, side effects, or semantics
- The resulting code must behave identically to the original.
Move Code Only
-
The refactor must be structural only
-
Allowed changes:
- Reordering functions
- Adding section headers
- Renaming internal/private functions consistently
-
Disallowed changes:
- Rewriting logic
- Simplifying implementations
- Changing APIs
- Changing imports unnecessarily
- Modifying formatting beyond what is required for reorganization
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 · 53 lines · 9 tokens per session scan A 3b7a52e6e0fe
coding.reorg_functions is a skill published in the GitHub repository causify-ai/helpers (145 stars, last pushed 2d ago), licensed Apache-2.0. It adds 9 tokens to every session and 366 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.