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/iurykrieger/claude-bedrock/setupnpx skills add iurykrieger/claude-bedrock --skill setupgit clone --depth 1 https://github.com/iurykrieger/claude-bedrockWrote 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/iurykrieger/claude-bedrock/setup)<a href="https://agentmods.dev/skills/iurykrieger/claude-bedrock/setup"><img src="https://agentmods.dev/badge/skills/iurykrieger/claude-bedrock/setup.svg" alt="Measured on agentmods" 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.00090 | $0.11638 |
| Opus 5 | $0.00045 | $0.05819 |
| Sonnet 5 | $0.00018 | $0.02328 |
| Haiku 4.5 | $0.00009 | $0.01164 |
Grade A, and why
setup scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Step 3 — curl (Python 3.10+ not available):** This is a copy
94% identical to setup — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bedrock:setup — Vault Initialization
Plugin Paths
Templates and entity definitions are in the plugin directory, not in the vault root. Use the "Base directory for this skill" provided at invocation to resolve paths:
- Entity definitions:
<base_dir>/../../entities/ - Templates:
<base_dir>/../../templates/{type}/_template.md - Plugin CLAUDE.md:
<base_dir>/../../CLAUDE.md(auto-injected into context)
Where <base_dir> is the path shown in "Base directory for this skill".
Overview
This skill bootstraps any folder into a fully functional Bedrock-powered Obsidian vault through an interactive guided flow. It creates directories, copies templates, configures the vault, scaffolds example entities with bidirectional wikilinks, checks dependencies, and guides the user through next steps.
You are a setup agent. Follow the phases below in order. Do not skip steps.
Phase 0 — Idempotency Check
Check if the vault is already initialized:
ls .bedrock/config.json 2>/dev/null
If .bedrock/config.json exists:
-
Read and display the current configuration:
This vault is already initialized: - Language: <language> - Preset: <preset> - Domains: <domains> - Git strategy: <git.strategy or "commit-push" if absent> - Initialized at: <date> -
Check if this vault is registered in the global vault registry:
cat <base_dir>/../../vaults.json 2>/dev/nullIf the registry exists, check if any entry has a
pathmatching the current working directory.- If registered: display "Registered as vault
<name>" alongside the config above. - If NOT registered: display "This vault is not yet registered in the global vault registry."
- If registered: display "Registered as vault
-
Ask the user:
"This vault is already initialized. What would you like to do?"
- Reconfigure — Update language, domains, git strategy, and regenerate vault CLAUDE.md (directories and entities are NOT touched)
- Register only — Register this vault in the global registry (if not already registered) without changing configuration
- Skip — Exit with no changes
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.
- 6d ago First seen · 1,304 lines · 90 tokens per session scan A 0033252b2e73
setup is a skill published in the GitHub repository iurykrieger/claude-bedrock (97 stars, last pushed 4mo ago), licensed MIT. It adds 90 tokens to every session and 11,638 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 94% identical to setup, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.