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 gpsaggese/helpers --skill coding.reorg_functionsgit clone --depth 1 https://github.com/gpsaggese/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/gpsaggese/helpers/coding.reorg_functions)<a href="https://agentmods.dev/skills/gpsaggese/helpers/coding.reorg_functions"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/coding.reorg_functions/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/gpsaggese/helpers/coding.reorg_functions"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/coding.reorg_functions.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.00009 | $0.00369 |
| Opus 5.5 | $0.00004 | $0.00148 |
| Sonnet 5.5 | $0.00002 | $0.00074 |
| 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 yesterday.
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 per the general rules in
coding.rules.md- Follow
## Organize Functions Into Logical Layersin.claude/skills/coding.rules.md - Follow
## Order Layers by Abstraction Levelin.claude/skills/coding.rules.md - Follow
## Order Functions Within Each Layerin.claude/skills/coding.rules.md - Follow
## Keep Related Functions Togetherin.claude/skills/coding.rules.md - Follow
## Mark Private Functionsin.claude/skills/coding.rules.md
- Follow
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
Verification
- Confirm every function from the original file is still present
- Run the file's unit tests to confirm behavior is unchanged
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.
- yesterday First seen · 54 lines · 9 tokens per session scan A 75b4dad3962a
coding.reorg_functions is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 369 once invoked, about $0.0000 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-11-06.
coding.reorg_functions compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| coding.reorg_functionsgpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 9 | Claude Code |
| matlabK-Dense-AI/scientific-agent-skills | Skill | 56k | 5d ago | MIT | A | 44 | Claude Code |
| pennylaneK-Dense-AI/scientific-agent-skills | Skill | 56k | 5d ago | MIT | A | 74 | Claude Code |
| holoscan-install-wheelNVIDIA/skills | Skill | 3.9k | today | Apache-2.0 | A | 34 | Claude Code, Codex |
| future-self-liteTHU-MAIC/OpenMAIC | Skill | 43k | yesterday | MIT | A | 20 | Claude Code, Codex |
| rocm-kernelshuggingface/kernels | Skill | 783 | yesterday | Apache-2.0 | A | 93 | Claude Code |
| typing-exclusion-workergetsentry/skills | Skill | 1.1k | yesterday | Apache-2.0 | A | 57 | Claude Code |