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/deepank308/hermes-swe-agent/setupnpx skills add Deepank308/hermes-swe-agent --skill setupgit clone --depth 1 https://github.com/Deepank308/hermes-swe-agentWhat 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.00036 | $0.01143 |
| Opus 5 | $0.00018 | $0.00571 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
setup 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 2d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Hosting Setup Guide
Help the user set up this infrastructure for their own repositories and AWS account. This is an interactive walkthrough — ask questions, validate inputs, and guide them through each step.
Important: Read SETUP.md and .env.example first for the full setup flow. Use the docs in docs/ as references for each integration.
Phase 1: Understand Their Setup
Ask the user about their environment:
- Which repositories will the agent work on? (GitHub org/repo names)
- AWS region preference (default: eu-north-1)
- Domain name they'll use for the orchestrator (e.g.
hermes.example.com) - Which integrations they want:
- Linear (required)
- GitHub App or PAT only? (recommend App for short-lived tokens)
- Slack notifications? (optional)
- Preview URLs with stable domains? (optional, needs Cloudflare API token)
Phase 2: Configure repos.json
Based on their answers:
- Read the current
repos.jsonandrepos.example.jsonto understand the format. - Edit
repos.jsonwith entries for their repositories. - For each repo, decide:
bakeAmi: true(heavy deps, Docker services) orfalse(lightweight, fast install)instanceTypebased on their repo's resource needsscriptsDirif they need custom boot scripts (explain when this is needed)
- Use
docs/repos-json.mdto guide the conversation.
Phase 3: Configure .env.local
- Help them create
.env.localfrom.env.example:cp .env.example .env.local - Walk through each section of
.env.exampleand help them fill in values. - For each integration, read the corresponding guide from
docs/:
Linear (required)
- Guide:
docs/linear.md - They need to create: OAuth app + webhook in Linear Settings
- Collect:
LINEAR_CLIENT_ID,LINEAR_CLIENT_SECRET,LINEAR_WEBHOOK_SECRET - Callback URL:
https://<their-domain>/oauth/callback - Webhook URL:
https://<their-domain>/webhook
GitHub (required)
- Guide:
docs/github.md GITHUB_TOKEN(PAT with repo scope) is always required for setup- Recommend also setting up a GitHub App for agent operations — collect
GITHUB_APP_CLIENT_ID,GITHUB_APP_PRIVATE_KEY,GITHUB_APP_INSTALLATION_ID
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.
- 2d ago First seen · 123 lines · 36 tokens per session scan A 8b4e0f63ec73
setup is a skill published in the GitHub repository Deepank308/hermes-swe-agent (11 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,143 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
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…