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 scott-fryxell/brayness --skill brayness-syncgit clone --depth 1 https://github.com/scott-fryxell/braynessWrote 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/scott-fryxell/brayness/brayness-sync)<a href="https://agentmods.dev/skills/scott-fryxell/brayness/brayness-sync"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/brayness-sync/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/scott-fryxell/brayness/brayness-sync"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/brayness-sync.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.00095 | $0.00759 |
| Opus 5.5 | $0.00038 | $0.00304 |
| Sonnet 5.5 | $0.00019 | $0.00152 |
| Haiku 4.5 | $0.00010 | $0.00076 |
Grade A, and why
brayness-sync 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 28d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brayness Sync
One-way copy: dev root -> skills/brayness-sync/published/ (the git-tracked mirror for
releases). Dev has working chaos (nested repos, secrets, sessions); the
mirror stays clean and publishable. Every sync is reviewed - no blind sync.
Copy list (source of truth)
| Path | Why |
|---|---|
skills/ |
skill catalog |
extensions/ |
extensions |
bin/ |
harness scripts and CLI wrapper |
prompts/ |
prompt templates |
package.json |
app dependency + scripts |
AGENTS.md, README.md |
agent docs |
.ignore, .nvmrc |
repo config |
.pi/agent/settings.json, .pi/agent/models.json |
pi config |
.pi/agent/npm/README.md, .pi/agent/npm/.gitignore |
add-on signposts |
.pi/agent/extensions |
symlink |
.cursor/skills, .claude/skills |
repo-root symlinks (Cursor/Claude Code) |
Never copy: .pi/agent/ anything else (auth, trust, caches, models-store,
sessions, npm/node_modules), .env*, nested .git/, node_modules/,
AGENTS.local.md, plans/, work/ projects, and skills/brayness-sync/published/ itself - the
mirror is the target, never a source.
The plans viewer now lives in work/brayness/examples/plan-viewer/ - a product
tree the mirror does not ship. package.json still names its scripts, so a
published npm run plans points at a path that stays on the dev machine.
What ships with it
3 files 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.
- 28d ago Changed · +5 lines · +4 tokens per session df72067c62fe
- 1mo ago Changed 4df841f41048
- 1mo ago First seen · 55 lines · 91 tokens per session scan A 65c142c46057
brayness-sync is a skill published in the GitHub repository scott-fryxell/brayness (125 stars, last pushed 29d ago), licensed MIT. It adds 95 tokens to every session and 759 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.