report-apexyard-bug

report-apexyard-bug is a skill for Claude Code from me2resh/apexyard. It costs 56 tokens per session (2,313 once invoked), scanned A, original, MIT.

A workflow for reporting defects in the public ApexYard framework itself, such as a broken hook, incorrect rule, missing skill, or wrong documentation. It files a structured issue in the framework's upstream GitHub repository.

In plain words
What is it for?
Use it to report framework misbehaviour, documentation errors, skill gaps, or rule problems upstream.
Why use it?
It separates framework defects from bugs in your own managed project and helps prevent private project information from being published.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Good fit Use it to report framework misbehaviour, documentation errors, skill gaps, or rule problems upstream.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/me2resh/apexyard/report-apexyard-bug
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 me2resh/apexyard --skill report-apexyard-bug
Clone the repo
git clone --depth 1 https://github.com/me2resh/apexyard

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 report-apexyard-bug

README.md
[![agentmods](https://agentmods.dev/badge/skills/me2resh/apexyard/report-apexyard-bug/github.svg)](https://agentmods.dev/skills/me2resh/apexyard/report-apexyard-bug)
Your own site
<a href="https://agentmods.dev/skills/me2resh/apexyard/report-apexyard-bug"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/report-apexyard-bug/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 report-apexyard-bug

Your own site · 80×15
<a href="https://agentmods.dev/skills/me2resh/apexyard/report-apexyard-bug"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/report-apexyard-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,313 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 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 Rogue Agent · line 41
    Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
    Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
  • high Tool Misuse · line 63
    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.
How audits are shown
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.00056 $0.02313
Opus 5.5 $0.00022 $0.00925
Sonnet 5.5 $0.00011 $0.00463
Haiku 4.5 $0.00006 $0.00231

Measured 15d ago against content hash 8cd973853d4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

report-apexyard-bug 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.

.claude/skills/report-apexyard-bug/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/report-apexyard-bug — Report a Framework Bug Upstream

Read .claude/rules/writing-standard.md. Use the controlled technical writing profile for the upstream bug report: lead with the observed outcome and reproducible next action.

Files a structured GitHub Issue about the apexyard framework itself to the canonical upstream me2resh/apexyard — for when a hook misfires, a skill is broken, a rule produces a wrong result, or the docs are wrong.

This is the framework-feedback sibling of /bug. The difference is the target:

Skill Reports a bug in… Files to…
/bug your managed project's code your project's own GitHub repo
/report-apexyard-bug the apexyard framework (hooks / skills / rules / agents / docs) 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 in the issue. Per .claude/rules/leak-protection.md, describe the context generically ("a registered project", "one of the managed workspaces"). The block-private-refs-in-public-repos.sh hook is the mechanical backstop, but scrub at authoring time — the private name is right there in your context while you write, and not referencing it takes active suppression.

Usage

/report-apexyard-bug detect-role-trigger.sh fires on the wrong path
/report-apexyard-bug /handover crashes when the repo has no README
/report-apexyard-bug require-active-ticket blocks an exempt docs edit

Process

0. Write the active-issue-skill marker (REQUIRED — me2resh/apexyard#268)

Before any gh issue create, write this skill's name to the active-issue-skill marker so require-skill-for-issue-create.sh lets the command through. At entry:

# 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 "report-apexyard-bug" > "$skill_marker"

Read the full file on GitHub · 207 lines

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. 15d ago Changed · +6 lines 8cd973853d4d
  2. 22d ago Changed · -9 lines 514009c9b44a
  3. 1mo ago Changed · +3 lines ffdc0eb9a95c
  4. 2mo ago First seen · 207 lines · 56 tokens per session scan A 766ea7a0ea58

Subscribe to this mod's changes

report-apexyard-bug is a skill published in the GitHub repository me2resh/apexyard (542 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 2,313 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.

Related

report-apexyard-bug compared with skills from other repositories

report-apexyard-bug next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
report-apexyard-bugme2resh/apexyardSkill542yesterdayMITA56Claude Code
debugparcadei/Continuous-Claude-v3Skill3.9k9mo agoMITA14Claude Code
skeptical-triageavelikiy/great_ctoSkill1122d agoMITA49Claude Code
anti-patternsavelikiy/great_ctoSkill1122d agoMITA59Claude Code
deploy-landedavelikiy/great_ctoSkill1122d agoMITA103Claude Code
signing-preflightavelikiy/great_ctoSkill1122d agoMITA105Claude Code
observability-baselineavelikiy/great_ctoSkill1122d agoMITA100Claude Code