coding.reorg_functions

coding.reorg_functions is a skill for Claude Code from gpsaggese/helpers. It costs 9 tokens per session (369 once invoked), scanned A, original, Apache-2.0.

A code-refactoring task that rearranges Python functions within one file without changing what the program does.

In plain words
What is it for?
Use it to organize a Python file into logical sections, keep public entry points easy to locate, and consistently rename private functions when needed.
Why use it?
It makes related functions easier to find and groups the file by levels of responsibility while preserving behavior, comments, and documentation.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

Good fit Use it to organize a Python file into logical sections, keep public entry points easy to locate, and consistently rename private functions when needed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/coding.reorg_functions
Install

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.

Any agent
npx skills add gpsaggese/helpers --skill coding.reorg_functions
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote 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.

agentmods badge for coding.reorg_functions

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/coding.reorg_functions/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/coding.reorg_functions)
Your own site
<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.

agentmods 80×15 button for coding.reorg_functions

Your own site · 80×15
<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>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 369 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 75b4dad3962a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/skills/coding.reorg_functions/SKILL.md · 54 lines

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 Layers in .claude/skills/coding.rules.md
    • Follow ## Order Layers by Abstraction Level in .claude/skills/coding.rules.md
    • Follow ## Order Functions Within Each Layer in .claude/skills/coding.rules.md
    • Follow ## Keep Related Functions Together in .claude/skills/coding.rules.md
    • Follow ## Mark Private Functions in .claude/skills/coding.rules.md

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
Changes

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.

  1. yesterday First seen · 54 lines · 9 tokens per session scan A 75b4dad3962a

Subscribe to this mod's changes

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.

Related

coding.reorg_functions compared with skills from other repositories

coding.reorg_functions next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
coding.reorg_functionsgpsaggese/helpersSkill158todayApache-2.0A9Claude Code
matlabK-Dense-AI/scientific-agent-skillsSkill56k5d agoMITA44Claude Code
pennylaneK-Dense-AI/scientific-agent-skillsSkill56k5d agoMITA74Claude Code
holoscan-install-wheelNVIDIA/skillsSkill3.9ktodayApache-2.0A34Claude Code, Codex
future-self-liteTHU-MAIC/OpenMAICSkill43kyesterdayMITA20Claude Code, Codex
rocm-kernelshuggingface/kernelsSkill783yesterdayApache-2.0A93Claude Code
typing-exclusion-workergetsentry/skillsSkill1.1kyesterdayApache-2.0A57Claude Code