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 me2resh/apexyard --skill request-apexyard-featuregit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/request-apexyard-feature)<a href="https://agentmods.dev/skills/me2resh/apexyard/request-apexyard-feature"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/request-apexyard-feature/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/request-apexyard-feature"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/request-apexyard-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 59 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.00047 | $0.02039 |
| Opus 5.5 | $0.00019 | $0.00816 |
| Sonnet 5.5 | $0.00009 | $0.00408 |
| Haiku 4.5 | $0.00005 | $0.00204 |
Grade A, and why
request-apexyard-feature 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/request-apexyard-feature — Request a Framework Feature Upstream
Read .claude/rules/writing-standard.md. Use the controlled technical writing profile for the
upstream feature request: state the outcome and reason before detail.
Files a structured GitHub Issue proposing a feature or enhancement for the
apexyard framework itself to the canonical upstream me2resh/apexyard —
for a new skill, a new hook, a rule improvement, a better workflow, etc.
This is the framework-feedback sibling of /feature. The difference is the target:
| Skill | Requests a feature for… | Files to… |
|---|---|---|
/feature |
your managed project | your project's own GitHub repo |
/request-apexyard-feature |
the apexyard framework (skills / hooks / rules / agents / workflows) | me2resh/apexyard (upstream) |
Leak protection (mandatory). This skill writes to a PUBLIC framework repo. NEVER include a registered private project's name, repo slug, or workspace path. Per
.claude/rules/leak-protection.md, describe the motivating context generically ("while onboarding a project", "during bulk ticket filing"). Theblock-private-refs-in-public-repos.shhook is the backstop; scrub at authoring time.
Usage
/request-apexyard-feature a /reindex skill for manual MCP reindexing
/request-apexyard-feature let /handover pick which docs to generate
/request-apexyard-feature a hook that warns on stale review markers
Process
0. Write the active-issue-skill marker (REQUIRED — me2resh/apexyard#268)
# Ops root through the session pin (docs/skills/shared/ops-root.md).
ops_root=$(p="${APEXYARD_OPS_PIN_DIR:-$HOME/.claude/apexyard}/ops-root-${CLAUDE_CODE_SESSION_ID:-}"; r=""; [ -z "${APEXYARD_OPS_DISABLE_PIN:-}" ] && [ -f "$p" ] && IFS= read -r r < "$p"; [ -f "$r/.claude/hooks/_lib-ops-root.sh" ] || { r="$PWD"; while [ -n "$r" ] && [ ! -f "$r/.claude/hooks/_lib-ops-root.sh" ]; do r=${r%/*}; done; }; [ -f "$r/.claude/hooks/_lib-ops-root.sh" ] && . "$r/.claude/hooks/_lib-ops-root.sh" && resolve_ops_root) && [ -n "$ops_root" ] || { echo "No ops root. See docs/skills/shared/ops-root.md." >&2; exit 1; }
mkdir -p "$ops_root/.claude/session"
marker_home="$ops_root"
. "$marker_home/.claude/hooks/_lib-session-markers.sh"
skill_marker=$(active_issue_skill_marker_path "$marker_home") || { echo "A session id is required. Restart through the harness adapter." >&2; exit 2; }
echo "request-apexyard-feature" > "$skill_marker"
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 · +6 lines 93cc64bcb844
- 22d ago Changed · -9 lines 402487c3b684
- 1mo ago Changed · +3 lines e0ff13b43eca
- 2mo ago First seen · 191 lines · 47 tokens per session scan A 85891749027b
request-apexyard-feature is a skill published in the GitHub repository me2resh/apexyard (542 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 2,039 once invoked, about $0.0002 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.
request-apexyard-feature compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| request-apexyard-featureme2resh/apexyard | Skill | 542 | yesterday | MIT | A | 47 | Claude Code |
| signing-preflightavelikiy/great_cto | Skill | 112 | 2d ago | MIT | A | 105 | Claude Code |
| commitparcadei/Continuous-Claude-v3 | Skill | 3.9k | 9mo ago | MIT | A | 12 | Claude Code |
| commitpedrohcgs/claude-code-my-workflow | Skill | 1.7k | 2d ago | MIT | A | 135 | Claude Code |
| moai-ref-git-workflowmodu-ai/moai-adk | Skill | 1.3k | 4d ago | Apache-2.0 | A | 58 | Claude Code |
| git-commitdecebals/claude-code-java | Skill | 770 | 8d ago | MIT | A | 38 | Claude Code, Codex |
| phx-pr-reviewoliver-kriska/claude-elixir-phoenix | Skill | 574 | yesterday | MIT | A | 61 | Claude Code, Codex |