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 0xHoneyJar/loa-freeside --skill cross-repo-status-readergit clone --depth 1 https://github.com/0xHoneyJar/loa-freesideWrote 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/0xhoneyjar/loa-freeside/cross-repo-status-reader)<a href="https://agentmods.dev/skills/0xhoneyjar/loa-freeside/cross-repo-status-reader"><img src="https://agentmods.dev/badge/skills/0xhoneyjar/loa-freeside/cross-repo-status-reader/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/0xhoneyjar/loa-freeside/cross-repo-status-reader"><img src="https://agentmods.dev/badge/skills/0xhoneyjar/loa-freeside/cross-repo-status-reader.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00051 | $0.01822 |
| Opus 5.5 | $0.00020 | $0.00729 |
| Sonnet 5.5 | $0.00010 | $0.00364 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
cross-repo-status-reader 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 9d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 174 lines · 51 tokens per session scan A 1c2774d7032d
cross-repo-status-reader is a skill published in the GitHub repository 0xHoneyJar/loa-freeside (8 stars, last pushed 27d ago), with no licence file. It adds 51 tokens to every session and 1,822 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-10-02.
Other skills, from other repositories
fix
Fix a tracker issue end-to-end, or batch-queue all open GitHub issues from a repo.
check
Queue a check mission for a GitHub PR or Issue (rebase, review, plan).
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…