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 agentmods add skills/amonstack/gitea_mcp/gitea-rerun-actionnpx skills add amonstack/gitea_mcp --skill gitea-rerun-actiongit clone --depth 1 https://github.com/amonstack/gitea_mcpWrote 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/amonstack/gitea_mcp/gitea-rerun-action)<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-rerun-action"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-rerun-action.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 | $0.00126 | $0.00793 |
| Opus 5 | $0.00063 | $0.00396 |
| Sonnet 5 | $0.00025 | $0.00159 |
| Haiku 4.5 | $0.00013 | $0.00079 |
Grade A, and why
gitea-rerun-action 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gitea-rerun-action
When to use
Trigger when the user asks to rerun / retry a workflow run or failed CI jobs — 中文请求如「重跑一下这个 CI」「再跑一次流水线」「只重试失败的 job」也 MUST 走本 skill：先确认运行已结束，经用户批准后再重跑。
Rerun one completed Actions workflow run. Tools: get_action_run, rerun_action_run, rerun_action_run_failed_jobs.
Prerequisites
- Resolve
owner+repo: pass explicitly, elseGITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, elseresolve_repo(gitea-resolve-repo). - Requires Gitea 1.26.0+ for the rerun endpoints. Rerunning consumes CI minutes and resources — always confirm the runId, the rerun scope (full vs failed-only), and the user's intent BEFORE calling either rerun tool.
Flow
- CHECK STATUS:
get_action_run({ runId })— verify the run has COMPLETED (status is one of: success, failure, cancelled, skipped). If still ACTIVE (queued, waiting, in_progress, running, pending), STOP — cannot rerun an active run; use gitea-cancel-action if you want to stop it first. - CHOOSE SCOPE:
rerun_action_run— reruns the ENTIRE run (all jobs, regardless of prior success/failure). Use when the run is fundamentally broken or you need a clean re-run.rerun_action_run_failed_jobs— reruns ONLY the jobs that failed. More efficient when most jobs succeeded; preserves the successful job results. The run must have conclusion "failure" for this to make sense.
- CONFIRM: state the runId, display_title, conclusion, and the chosen scope, then ask the user for explicit approval.
- RERUN:
rerun_action_run({ runId })orrerun_action_run_failed_jobs({ runId }). - VERIFY (optional): call
list_action_runsto find the new run (it will have an incrementedrun_attempt).
rerun_action_run
- RULES:
runIdis the numeric run ID. Only COMPLETED runs can be reruned. Creates a NEW run; the original is not modified. Returns the new run object or a text confirmation. - CHECK FIRST:
get_action_run(step 1) + scope decision (step 2) + user confirmation (step 3).
rerun_action_run_failed_jobs
- RULES: same as rerun_action_run but only re-executes failed jobs. Only meaningful when the run's conclusion is "failure". Returns a text confirmation.
- CHECK FIRST:
get_action_runto confirm the run has failed jobs + user confirmation.
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 · +4 lines · +44 tokens per session 23820672a474
- 4d ago First seen · 34 lines · 82 tokens per session scan A 537c13be6d23
gitea-rerun-action is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 793 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.