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 gtrabanco/agentic-workflow --skill resolve-repository-stategit clone --depth 1 https://github.com/gtrabanco/agentic-workflowWrote 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/gtrabanco/agentic-workflow/resolve-repository-state)<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/resolve-repository-state"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/resolve-repository-state.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00662 |
| Opus 5 | $0.00024 | $0.00331 |
| Sonnet 5 | $0.00010 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
resolve-repository-state 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Repository State
Resolve evidence conflicts explicitly and publish the next frozen snapshot.
Turn contract
✓ A named contradiction and both evidence sources were read
✓ The disposition is accepted, rejected, or needs-input
✓ Accepted/rejected results publish a frozen snapshot; needs-input stops without freezing
✓ No unrelated fact or decision changed
✓ The closing → Next: block is printed last
Step 0 — Discover the project (always first)
Read the agent guide, documentation map, frozen ledger, and the requested contradiction before deciding anything.
Process
- Read the frozen ledger and the contradiction row named by the user.
- Verify both the frozen fact's evidence and the proposed new evidence.
- Choose one result: accept new evidence, reject it, or request human input.
- If human input is required, update the contradiction row with the exact
missing evidence or decision, keep snapshot status
contradicted, and stop without incrementing the snapshot identifier or publishing a frozen snapshot. - For an accepted result, supersede the fact or decision with a new row that cites both evidence sources. For a rejected result, retain the fact and record why.
- For accepted or rejected results only, update the contradiction row,
increment the snapshot identifier, set status to
frozen, and record the next frozen snapshot's source revision.
Guardrails
- This skill is the sole writer for updates to frozen facts and accepted decisions.
- A consumer may propose a contradiction but never resolve it inline.
- Inference and documentation alone are insufficient to update a fact.
Portability
Without a slash menu, open this file and follow its process in a fresh turn.
Relationship to other skills
Consumes contradictions from every workflow role and produces the snapshot that
discovery, planning, execution, review, and audit reuse. The contradiction's
Reported by field identifies the interrupted role to resume; resolution never
defaults a review, audit, or status interruption to planning.
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.
- 4d ago Changed · +1 lines df8cb6bf622a
- 8d ago First seen · 80 lines · 48 tokens per session scan A 5e51eaf26225
resolve-repository-state is a skill published in the GitHub repository gtrabanco/agentic-workflow (21 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 662 once invoked, about $0.0002 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-30.
Other skills, from other repositories
apply-semantic-versioning
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes…
commit-changes
Stage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the…
configure-git-repository
Configure a Git repository with proper .gitignore, branch strategy, commit conventions, hooks, and remote setup. Covers initial setup and common patterns for R, Node.js, and Python projects. Use when initializing version control for a new project, adding a .gitignore for a specific language or framework, setting up…
create-github-release
Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or…
create-pull-request
Create and manage pull requests using GitHub CLI. Covers branch preparation, writing PR titles and descriptions, creating PRs, handling review feedback, and merge/cleanup workflows. Use when proposing changes from a feature or fix branch for review, merging completed work into the main branch, requesting code review…
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.