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/cocorof/geny-executor/simplifynpx skills add CocoRoF/geny-executor --skill simplifygit clone --depth 1 https://github.com/CocoRoF/geny-executorWhat 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.00034 | $0.01061 |
| Opus 5 | $0.00017 | $0.00531 |
| Sonnet 5 | $0.00007 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
Simplify 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify — three-pass code review
Run three passes over the target. Keep each pass narrow: don't let the reuse reviewer second-guess the quality reviewer, etc. After all three passes, synthesise — pick the smallest set of changes that improves the most dimensions.
Step 0: Locate the target
The user passed ${target}. Resolve it:
- If empty, default to the current diff vs the merge base of HEAD
(or vs
main/masterwhen the merge base is hard to find):git diff --name-only origin/main...HEAD 2>/dev/null || git diff --name-only HEAD~1 2>/dev/null || git ls-files --modified - If a path: read it directly (or, for a directory, glob for code files).
- If a git range (e.g.
HEAD~3..HEAD,feature-branch...main): walk the diff.
If the target turns up empty, stop and ask the user what they'd like reviewed.
Step 1 — Reuse pass
Pass criterion: what is being re-implemented that already exists?
Look for:
- Utility functions duplicated across files. Same logic, different imports.
- Inline implementations that bypass an existing helper / library the project already depends on.
- Constants / enums redeclared per-call-site instead of imported once.
- Shape coercion / conversion code that an existing serializer already handles.
Output (this pass): bullet list of duplicated / re-implemented things, each with the existing canonical location + the new duplicate location.
Step 2 — Quality pass
Pass criterion: what would a reviewer flag in a PR comment?
Look for:
- Names that don't match what they hold (
data,temp,info). - Functions doing more than one thing (and / or in the function signature is a tell).
- Error handling that swallows information (
except: pass, raw rethrow with no context). - Comments that no longer describe the code.
- Dead code (unreachable branches, unused imports / params, no callers).
- Magic numbers that lack a named constant.
Output (this pass): bullet list, each item naming the file:line + the smell.
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 · 124 lines · 34 tokens per session scan A c7f06b5e6a8b
Simplify is a skill published in the GitHub repository CocoRoF/geny-executor (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,061 once invoked, about $0.0002 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-31.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
unit-converter
Convert between common units using a multiplication factor. Use when asked to convert miles, kilometers, pounds, or kilograms.