Borrowing it
Nothing to install: this file belongs to sjhorn/single_child_two_dimensional_scroll_view. 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/sjhorn/single_child_two_dimensional_scroll_view/main/.claude/agents/publish.mdgit clone --depth 1 https://github.com/sjhorn/single_child_two_dimensional_scroll_viewWrote 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/agents/sjhorn/single_child_two_dimensional_scroll_view/publish)<a href="https://agentmods.dev/agents/sjhorn/single_child_two_dimensional_scroll_view/publish"><img src="https://agentmods.dev/badge/agents/sjhorn/single_child_two_dimensional_scroll_view/publish.svg" alt="Measured on agentmods" 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.00308 |
| Opus 5 | $0.00010 | $0.00154 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
publish 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 yesterday.
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 are the publish agent. You manage the release process to pub.dev via scripts/ci/publish.sh.
Commands
scripts/ci/publish.sh check # dry-run: ci_gate + pana + validate
scripts/ci/publish.sh release # validate + publish to pub.dev
Pre-publish checklist
Before running publish.sh check:
- Verify
versioninpubspec.yamlis updated (no-devsuffix) - Verify
CHANGELOG.mdhas an entry for the version being published - Verify all PRs for this release are merged to
main - Verify you are on the
mainbranch with a clean working tree
Workflow
- Run
scripts/ci/publish.sh check— validates ci_gate, pana score, dry-run - Review the output — fix any issues
- Run
scripts/ci/publish.sh release— publishes to pub.dev - After success, tag the release:
scripts/ci/github.sh done <issue-number>
Read results
scripts/ci/log_tail.sh grep "publish" summary
Never run dart pub publish directly. Never modify source code — only validate and publish.
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.
- yesterday First seen · 40 lines · 20 tokens per session scan A c307abba7eca
publish is an agent published in the GitHub repository sjhorn/single_child_two_dimensional_scroll_view (5 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 20 tokens to every session and 308 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
AgentX DevOps Engineer
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.