Borrowing it
Nothing to install: this file belongs to AlexanderMattTurner/agent-glovebox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AlexanderMattTurner/agent-glovebox/main/.github/prompts/agent-publish-manifest.mdgit clone --depth 1 https://github.com/AlexanderMattTurner/agent-gloveboxWrote 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/commands/alexandermattturner/agent-glovebox/agent-publish-manifest)<a href="https://agentmods.dev/commands/alexandermattturner/agent-glovebox/agent-publish-manifest"><img src="https://agentmods.dev/badge/commands/alexandermattturner/agent-glovebox/agent-publish-manifest/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/commands/alexandermattturner/agent-glovebox/agent-publish-manifest"><img src="https://agentmods.dev/badge/commands/alexandermattturner/agent-glovebox/agent-publish-manifest.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.00000 | $0.00699 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
agent-publish-manifest 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 6d 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.
What it actually says
You hold no GitHub credential in this run. git push, gh pr create, gh pr close and gh issue all fail, because the workflow keeps the write token out of your shell.
Commit your work locally as usual — git checkout -b, git add, git commit need no credential — then declare what you want published. The workflow's publish step performs that list under its own token. It is a fixed list of actions, and the workflow pins each one's target: which base branch a pull request opens against, which tracking issue the issue verb rewrites, which pull requests you may close, and which issues you may comment on. .github/scripts/agent_publish.py is the whole list.
Write one JSON object to $RUNNER_TEMP/agent-publish/manifest.json. Create the directory first. Every key is optional; an unknown key fails the step.
{
"pull_request": {
"title": "fix(security): weekly vulnerability remediation",
"body_file": "/path/to/pr-body.md",
"labels": ["security-scan"]
},
"close_pull_requests": [412, 413],
"issue": {
"title": "the scanner reports a new advisory with no upstream fix",
"body_file": "/path/to/issue-body.md",
"labels": ["security-scan"]
},
"issue_comments": [{ "number": 907, "body_file": "/path/to/comment.md" }]
}
Shipping nothing is the whole manifest instead, never a key beside the others:
{ "nothing_to_publish": "every alert was already covered by an open triage PR" }
What each key does:
pull_request— pushes the branch you are on and opens its pull request, or rewrites the title and body of the open one that branch already has. Create a branch first: the step refuses to push when HEAD is still the base branch. Commit everything too — it refuses a worktree with uncommitted changes to tracked files, because no pull request would carry them.close_pull_requests— closes each number with the commentSuperseded by #<your PR>.Needspull_requestin the same manifest. The step refuses a number whose head branch is outside what this job may subsume.issue— rewrites this job's own tracking issue, or opens it. The workflow names that issue with a hidden marker, and the step adds the marker itself; you cannot select a different issue.labelsapply only when it opens a new one.issue_comments— one comment per entry. The step refuses a number outside the set the workflow staged for this run.nothing_to_publish— your reason for shipping nothing. It must be the manifest's only key, and you must have made no commit.
Each body_file holds the finished text, written by you, under $RUNNER_TEMP or the workspace. The step refuses an empty file and a path outside those two directories.
Any commit you make must be published by a pull_request in this manifest. A commit with no manifest, a commit beside nothing_to_publish, and a commit whose manifest declares only an issue are all errors — each would drop your work, so the step reds instead.
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.
- 6d ago First seen · 41 lines · 0 tokens per session scan A 16959f6525e2
agent-publish-manifest is a command published in the GitHub repository AlexanderMattTurner/agent-glovebox (63 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 699 tokens. 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-06.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.