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 jame581/LogseqBrain --skill releasegit clone --depth 1 https://github.com/jame581/LogseqBrainWrote 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/jame581/logseqbrain/release)<a href="https://agentmods.dev/skills/jame581/logseqbrain/release"><img src="https://agentmods.dev/badge/skills/jame581/logseqbrain/release/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/jame581/logseqbrain/release"><img src="https://agentmods.dev/badge/skills/jame581/logseqbrain/release.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.00047 | $0.00620 |
| Opus 5.5 | $0.00019 | $0.00248 |
| Sonnet 5.5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
release 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 today.
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release logseq-brain
CONTRIBUTING.md § Releasing a new version is the source of truth. Read it now, in full, and follow it step by step. This skill only adds the order of operations and the checks that have slipped before.
Argument: the version X.Y.Z. If none was given, read plugin/.claude-plugin/plugin.json and ROADMAP.md and ask which version to cut.
Before step 0
- The version branch
vX.Y.Zis merged tomainby PR, and the localmainis pulled. Releases are cut frommain. git statusis clean.
Gates — stop and report on any failure
- The
testsworkflow is green on the release commit:gh run list --branch main --limit 3. - The eval suite passes on the release commit. It runs only as the
logseq-evalWSL user and draws on plan usage, so ask before launching it. Use the/evalskill. Record theload-digestandsave-basictool-call figures for the release notes.
Mechanical steps
- Bump both
plugin/.claude-plugin/plugin.json"version"andBRAIN_VERSIONinplugin/skills/_shared/bin/brain. Theversion-matches-plugingolden case fails until they agree, so runsh tests/run.sh 'version-*'. - Annotate the version's design spec with the release measurement if the spec calls for it. Never rewrite the spec body.
- Commit with
chore(release): prepare vX.Y.Z, then tag it annotated and push the tag. Confirm with the user before pushing. - Create the GitHub release (
gh release create vX.Y.Z --notes-file …). Draft the notes from the commits since the previous tag, and include the eval figures.
After the tag — the steps that get forgotten
- Rebuild the Cowork archive from the tag and verify the listing: it must contain
skills/_shared/bin/brainandskills/_shared/lib/core.awk, and must not containtests/ortools/. - Bump
.claude-plugin/marketplace.jsonin the sibling../skillsmithrepo. First rungit -C ../skillsmith pull, and never assert its state from memory. That repo has its own commit and push. Confirm before pushing. - Update the logseq-brain project page in the brain with the release (
/brain-save).
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.
- today Changed ad5df4eb3335
- 25d ago First seen · 37 lines · 47 tokens per session scan A 32edc61a7e62
release is a skill published in the GitHub repository jame581/LogseqBrain (18 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 620 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-28.
Other skills, from other repositories
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…