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 agent-hub-initgit 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/agent-hub-init)<a href="https://agentmods.dev/skills/berkcangumusisik/agent-hub/agent-hub-init"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/agent-hub/agent-hub-init/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/agent-hub-init"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/agent-hub/agent-hub-init.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.00072 | $0.00724 |
| Opus 5 | $0.00036 | $0.00362 |
| Sonnet 5 | $0.00014 | $0.00145 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
agent-hub-init 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-hub-init
Create a project profile so the super-team specializes to this codebase.
Steps
-
Detect the stack. Inspect the repo to infer language, framework, package manager, database, and the real commands. Look at, as relevant:
package.json(scripts, deps) → Node/TS, framework, npm/pnpm/yarnpom.xml/build.gradle→ Java, Maven/Gradle, Springpyproject.toml/requirements.txt→ Python (Django/FastAPI/Flask)pubspec.yaml→ Flutter/Dart;app.json/expo→ React Native (Expo)go.mod→ Go;Cargo.toml→ RustGemfile→ Ruby/Rails;composer.json→ PHP/Laravel;*.csproj→ C#/.NETDockerfile,.github/workflows/, CI config → devops target- existing
README.mdfor run/test/build commands
If a matching starter template exists in this plugin (
templates/profiles/), use it as the baseline and adjust to what you actually find — faster and more accurate than from scratch.
1b. Detect monorepos. If you see workspaces (pnpm-workspace.yaml, package.json
workspaces, multiple apps/* or packages/*, a Gradle multi-module build), say so. Either
write one profile that names the sub-projects and their stacks, or recommend a profile per
workspace package. Don't flatten a monorepo into a single wrong stack.
-
Pick the active team. Choose from the profile's stack:
- backend project →
tech-lead, architect, backend-engineer, code-reviewer, qa-tester, security-reviewer - frontend →
tech-lead, architect, frontend-engineer, code-reviewer, qa-tester - mobile →
tech-lead, architect, mobile-engineer, code-reviewer, qa-tester - fullstack → include backend + frontend
- add
devops-engineerwhen CI/containers exist,tech-writerwhen docs matter
- backend project →
-
Write the files (do not overwrite without confirming if they already exist):
.claude/agent-hub/profile.yml— fill every field you detected; leave unknowns as""and tell the user what to fill..claude/CLAUDE.md— short project context that imports the profile via@.claude/agent-hub/profile.yml, plus stack summary, key commands, and conventions.
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 · 44 lines · 72 tokens per session scan A 9d77507bec63
agent-hub-init is a skill published in the GitHub repository berkcangumusisik/agent-hub (14 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 724 once invoked, about $0.0004 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.