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.00091 | $0.00680 |
| Opus 5 | $0.00046 | $0.00340 |
| Sonnet 5 | $0.00018 | $0.00136 |
| Haiku 4.5 | $0.00009 | $0.00068 |
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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brayness Sync
One-way copy: dev root -> work/sync/ (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 |
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/subagents.json |
subagent config (defaults, tools, profiles) |
.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.
Sessions rule: transcripts may contain secrets or personal info. They stay in dev, always.
Workflow
- Detect - diff dev against the mirror for the copy-list paths; summarize what changed.
- Plan - show what will be copied and excluded; get approval.
- Copy - commands in
references/workflow.md. - Validate - checks in
references/validation.md(no nested.git, no.env, nonode_modules, structure intact). Stop on any failure. - Review -
git diffin the mirror; walk the user through it. - Commit - propose a message; commit only after approval.
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.
- 2d ago Changed 4df841f41048
- 11d 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 (120 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 680 once invoked, about $0.0005 per session on Opus 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
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.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.