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/mathews-tom/armory/package-optimizernpx skills add Mathews-Tom/armory --skill package-optimizergit clone --depth 1 https://github.com/Mathews-Tom/armoryWhat 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.00110 | $0.01135 |
| Opus 5 | $0.00055 | $0.00567 |
| Sonnet 5 | $0.00022 | $0.00227 |
| Haiku 4.5 | $0.00011 | $0.00113 |
Grade A, and why
package-optimizer 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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Optimizer
Turn existing package evidence into one bounded, reviewable proposal. The optimizer is proposal-only: it never edits a package, changes a profile, or starts a benchmark run.
Scope
| Situation | Action |
|---|---|
| One package has current evaluator evidence | Propose one disposition. |
| A bounded family shares the same evidence/profile | Propose one family plan with a per-package row. |
| Evidence is missing, stale, structurally invalid, or from another profile | Return inconclusive; name the unresolved package decision and request the smallest recertification needed. |
| User asks to apply a proposal | Require explicit approval, preserve before artifacts, then hand the edit to the normal package workflow. |
| User asks for a broad benchmark before identifying a package decision | Refuse the expansion; identify the package decision first. |
Required inputs
- Package scope — one
type/namepackage or an explicitly bounded family. - Current evidence — static conformance and relevant eval-case result or a recorded behavioral result. Cite exact commands, artifacts, or case IDs.
- Capability profile — model/client/tool-surface identity when behavioral evidence depends on one. Structural-only evidence is labelled as such.
- Decision question — what behavior should be retained, simplified, or strengthened.
Do not infer effectiveness from package length, heading count, or static score.
Evidence validity
Reject evidence when any condition holds:
- package path, version, or evaluator case differs from the proposed scope;
- a behavioral result has no model/client/tool-surface identity;
- a profile is older than a recorded package change or cannot be compared to the requested profile;
- the evidence omits a failure, safety outcome, or relevant evaluator result;
- an M4 recertification report pools model targets or lacks complete cells.
A rejection uses the single output format below with Disposition: inconclusive,
Proposed change: none, and Approval required: yes. Its Unresolved package decision must name the package scope and decision question. A recertification
request repeats that exact field; do not request a benchmark without it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 117 lines · 110 tokens per session scan A b65c61c82966
package-optimizer is a skill published in the GitHub repository Mathews-Tom/armory (316 stars, last pushed 5d ago), licensed MIT. It adds 110 tokens to every session and 1,135 once invoked, about $0.0006 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
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
weekly-retro
Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
idea
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT…