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 asysta-act/agent-flow --skill publishgit clone --depth 1 https://github.com/asysta-act/agent-flowWrote 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/asysta-act/agent-flow/publish)<a href="https://agentmods.dev/skills/asysta-act/agent-flow/publish"><img src="https://agentmods.dev/badge/skills/asysta-act/agent-flow/publish/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/asysta-act/agent-flow/publish"><img src="https://agentmods.dev/badge/skills/asysta-act/agent-flow/publish.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.00020 | $0.04303 |
| Opus 5.5 | $0.00008 | $0.01721 |
| Sonnet 5.5 | $0.00004 | $0.00861 |
| Haiku 4.5 | $0.00002 | $0.00430 |
Grade A, and why
publish scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --proto "=http,https" --max-time 5 --retry 0 -X POST -H "Content-Type: application/json" \ How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish
Publish current work: PR + (conditional) issue tracker state change. Read Automation Config from CLAUDE.md.
/publish auto-detects the publishing mode from the current branch name and the Automation Config Source Control → Branch naming template. There are three success modes (full-publish, pr-only-no-id, pr-only-404) and one failure mode (FAIL). No flags. No new config keys. The "PR-only with valid tracker reference" use case is expressed by renaming the branch to one that does not match the configured Branch naming prefix (e.g., chore/refactor-foo instead of fix/PROJ-123-foo).
Operator note (interactive-only):
/publish is interactive-only— it requires user confirmation flows in agent prose and may FAIL in environments without an MCP server configured (CI / cron). For headless / batch publishing, use/agent-flow:autopilot.
Steps
Step 0 — Branch parse (NEW pre-pre-flight)
This step runs BEFORE the MCP pre-flight. It determines whether the tracker is needed at all.
0a. Resolve the current branch name.
branch_name=$(git branch --show-current)
If branch_name is empty, the working tree is in a detached HEAD state. There is no active branch to push or to use as the PR source, so /publish cannot proceed. FAIL with a single-line INFO message and EXIT non-zero:
[agent-flow][INFO] Cannot determine branch (detached HEAD). /publish requires an active branch.
This is a pre-flight environment check — NOT a tracker-down failure — so it does NOT use the [agent-flow] 🔴 Pipeline Block template. No tracker comment is posted. No webhook event is fired. (Detached HEAD is treated as FAIL — exit non-zero — NOT as pr-only-no-id, because there is no branch to push or use as PR source.)
0b. Read Source Control → Branch naming from Automation Config.
The template uses {issue-id} (and optionally {description}) as placeholders — for example fix/{issue-id}-{description} or feature/{issue-id} (per docs/reference/automation-config.md Branch naming row).
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.
- 2mo ago First seen · 327 lines · 20 tokens per session scan A c672d0dd8359
publish is a skill published in the GitHub repository asysta-act/agent-flow (12 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 4,303 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
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.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
thrunt-complete-milestone
Archive completed milestone and prepare for next version.
github
Use the GitHub CLI (gh) to inspect and manage repositories, pull requests, issues, workflows, releases, and API calls from the terminal. Use when a user asks to use gh/GitHub CLI, run GitHub repo or PR workflows, automate GitHub Actions from shell, or troubleshoot gh authentication and configuration.