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 berkcangumusisik/agent-hub --skill decision-loggit clone --depth 1 https://github.com/berkcangumusisik/agent-hubWrote 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/berkcangumusisik/agent-hub/decision-log)<a href="https://agentmods.dev/skills/berkcangumusisik/agent-hub/decision-log"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/agent-hub/decision-log/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/berkcangumusisik/agent-hub/decision-log"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/agent-hub/decision-log.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.00053 | $0.00338 |
| Opus 5 | $0.00026 | $0.00169 |
| Sonnet 5 | $0.00011 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
decision-log 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 10d 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
decision-log
Maintain a lightweight ADR log at .claude/agent-hub/decisions/ — the team's memory.
Recording a decision
- Create
.claude/agent-hub/decisions/if it doesn't exist. - Find the next number: count existing
NNNN-*.mdfiles and increment (start at0001). - Write
.claude/agent-hub/decisions/NNNN-<kebab-title>.mdwith these sections:- Title, Status (Accepted), Date (absolute, e.g. 2026-06-26), Deciders
- Context — the problem and forces at play
- Decision — what was chosen
- Alternatives considered — each option and why not
- Consequences — trade-offs, what gets easier/harder Keep it short and concrete.
- Confirm the saved path back to the user.
Reading decisions
When orienting to a project (or asked "why did we do X"), read the files under
.claude/agent-hub/decisions/ and honor them — do not silently contradict an accepted
decision. If new work conflicts with one, flag it and propose superseding the ADR.
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.
- 10d ago First seen · 28 lines · 53 tokens per session scan A 27c54e727bcc
decision-log is a skill published in the GitHub repository berkcangumusisik/agent-hub (14 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 338 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
omnigent-knowledge
Deep reference on Omnigent config format, executor types, skill/tool structure, and conventions. Load when you need to look up how the platform works.
build-omnigent
Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
detect-framework
Detect Python agent frameworks from code imports and map them to Omnigent executor types. Load when the user has existing agent code to integrate.
api-docs
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.
migration-guide
Turn a breaking change (an API rename, removed flag, changed default, or moved module) into concrete upgrade steps with before/after examples. Use when the user asks how to migrate, upgrade, or adapt to a breaking change.