Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/me2resh/apexyardnpx agentmods add skills/me2resh/apexyard/updateWrote 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/me2resh/apexyard/update)<a href="https://agentmods.dev/skills/me2resh/apexyard/update"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/update/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/me2resh/apexyard/update"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 127 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 240 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 1078 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00027 | $0.14067 |
| Opus 5.5 | $0.00011 | $0.05627 |
| Sonnet 5.5 | $0.00005 | $0.02813 |
| Haiku 4.5 | $0.00003 | $0.01407 |
Grade A, and why
update 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 15d 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 — 1,166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update — Sync ApexYard Fork from Upstream
Read .claude/rules/writing-standard.md. Use the controlled technical writing profile for the sync
PR body and migration notes. Lead with the outcome and next action.
Single-command replacement for the manual "fetch → branch → merge → push → PR" dance that fork maintainers do to pull upstream apexyard changes into their ops fork.
Path resolution
Read the registry path via portfolio_registry, the per-project docs dir via portfolio_projects_dir, and the ideas backlog via portfolio_ideas_backlog — all from .claude/hooks/_lib-portfolio-paths.sh. Source the helper at the top of any bash block that touches those paths:
source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-read-config.sh"
source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-portfolio-paths.sh"
registry=$(portfolio_registry)
Defaults match today's single-fork layout (./apexyard.projects.yaml, ./projects, ./projects/ideas-backlog.md). Adopters in split-portfolio mode override the portfolio.{registry, projects_dir, ideas_backlog} keys in .claude/project-config.json. Don't hardcode literal apexyard.projects.yaml or projects/ paths in bash blocks — the helper resolves whichever mode the adopter is in. See docs/multi-project.md.
Usage
/update # merge-based sync (default, safer)
/update --rebase # rebase local customisations on top of upstream
/update --dry-run # preview only, don't touch anything
/update --from-version v1.2.0 # override the version anchor (use when fork anchor is missing/wrong)
/update --skip-migrations # files-only sync; do NOT run the per-version migration chain
/update --skip-adapter-sync # do not refresh an already-installed Codex adapter
/update --from-dev # (hidden) pull from upstream/dev — pre-release; expect breakage
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.
- 15d ago Changed · +9 lines 0494f0ba38fd
- 29d ago Changed · +37 lines ba744f11c1c8
- 1mo ago Changed · +6 lines 8d8088e6a80a
- 1mo ago Changed · +14 lines 6a8edec55217
- 1mo ago Changed · +4 lines 128e50e5a895
- 2mo ago First seen · 1,096 lines · 27 tokens per session scan A 5417b749f70a
update is a skill published in the GitHub repository me2resh/apexyard (542 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 14,067 once invoked, about $0.0001 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-09-03.
update compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| updateme2resh/apexyard | Skill | 542 | yesterday | MIT | A | 27 | Claude Code |
| releaseparcadei/Continuous-Claude-v3 | Skill | 3.9k | 9mo ago | MIT | A | 20 | Claude Code |
| releaseYeachan-Heo/oh-my-claudecode | Skill | 41k | yesterday | MIT | A | 27 | Claude Code |
| changelog-generatordecebals/claude-code-java | Skill | 770 | 8d ago | MIT | A | 40 | Claude Code, Codex |
| releaseoliver-kriska/claude-elixir-phoenix | Skill | 574 | yesterday | MIT | A | 60 | Claude Code |
| ln-62-release-publisherlevnikolaevich/claude-code-skills | Skill | 587 | yesterday | MIT | A | 24 | Claude Code |
| land-and-deployFlorianBruniaux/claude-code-ultimate-guide | Skill | 6.4k | 2d ago | CC-BY-SA-4.0 | A | 24 | Claude Code |