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.
git clone --depth 1 https://github.com/jayvee/aigonWrote 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/jayvee/aigon/aigon-feature-push)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-feature-push"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-push/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/jayvee/aigon/aigon-feature-push"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-push.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.00161 |
| Opus 5.5 | $0.00000 | $0.00064 |
| Sonnet 5.5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
aigon-feature-push 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 1mo 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
aigon-feature-push
Push the current feature branch to origin with upstream tracking, making it available for pull request creation on GitHub.
This command does not alter workflow state, move specs, merge anything, or call agent-status. It is a simple git push -u origin <branch>.
Argument resolution
- In a feature worktree, run this with no arguments and Aigon will infer the current feature branch.
- In the main repo or from a non-feature branch, pass
<ID>and optionally[agent].
Run
aigon feature-push $ARGUMENTS
Examples:
aigon feature-push
aigon feature-push 55
aigon feature-push 55 ag
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.
- 1mo ago First seen · 25 lines · 0 tokens per session scan A 278d9984719b
aigon-feature-push is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 161 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-03.
Other commands, from other repositories
mach12:pr-pre-merge
Run the pre-merge checklist - branch freshness, docs, version, CHANGELOG, tests, CI.
mach12:issue-implement
Implement a specific stage of an issue's implementation plan.
mach12:pr-review
Run a comprehensive PR review with independent reviewers and post the results as a structured comment.
mach12:pr-create
Create a pull request for the current branch with structured description.
mach12:pr-merge
Merge a PR, delete the feature branch, and optionally create a release.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.