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 discover-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/discover-repository-state)<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/discover-repository-state"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/discover-repository-state/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/gtrabanco/agentic-workflow/discover-repository-state"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/discover-repository-state.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.00680 |
| Opus 5 | $0.00033 | $0.00340 |
| Sonnet 5 | $0.00013 | $0.00136 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
discover-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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover Repository State
Create a reviewable evidence snapshot before planning or implementation.
Turn contract
✓ Repository evidence was read or commands were run for every fact
✓ Facts, documentation, planned work, decisions, and inference are separated
✓ Snapshot status is frozen unless a contradiction was recorded
✓ No accepted decision or existing frozen fact was silently changed
✓ The closing → Next: block is printed last
Step 0 — Discover the project (always first)
Read the agent guide, documentation map, and any existing repository-state ledger before collecting evidence.
Process
- Read the project guide, documentation map, and any existing
docs/workflow/REPOSITORY_STATE.md. - Inspect repository files, tests, git state, and declared tooling. Record only directly observed statements in Repository Facts, each with file:line or command evidence.
- Record design records under Accepted Decisions, roadmap entries under Planned work, and document-only claims under Documentation. Do not copy them into facts without separate implementation evidence.
- Place reasoning under Inference and unresolved ambiguity under Open Questions.
- If the existing snapshot is already
contradicted, preserve that status and do not alter its unresolved contradiction; hand off toresolve-repository-state. Otherwise, if new evidence conflicts with a frozen fact, append a Contradiction, set snapshot status tocontradicted, and do not alter the fact. Hand off toresolve-repository-state. - Only if neither an existing nor a newly recorded contradiction is present,
set the snapshot status to
frozen. Commit the artifact and cite the source revision.
Guardrails
- Discovery records repository facts and preserves decisions, planned work, documentation, inference, questions, and contradictions in their own sections.
- The repository remains authoritative; refresh when the snapshot is stale.
- Never create implementation recommendations or silently accept decisions.
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.
- 5d ago Changed · +1 lines ac3b349a89f3
- 9d ago First seen · 84 lines · 66 tokens per session scan A 066f9de744d6
discover-repository-state is a skill published in the GitHub repository gtrabanco/agentic-workflow (21 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 680 once invoked, about $0.0003 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
think-like-me
Personal engineering rules and reasoning patterns the user has curated over time. Consult BEFORE writing, modifying, debugging, or designing any technical feature — rules often cover domain-specific gotchas (e.g., mobile audio timers need background mode) that generic answers miss. Also triggers on /learn-this, "learn…
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-k8s-attacks
Kubernetes cluster attack techniques covering the full attack lifecycle from initial foothold in a pod to cluster-wide compromise. Covers service account token theft and impersonation, RBAC misconfiguration exploitation including wildcard permissions and privilege escalation via role binding, direct etcd access for…
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…