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/vasallo94/obsidian-mcp-server/git-workflownpx skills add Vasallo94/obsidian-mcp-server --skill git-workflowgit clone --depth 1 https://github.com/Vasallo94/obsidian-mcp-serverWrote 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/vasallo94/obsidian-mcp-server/git-workflow)<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/git-workflow"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/git-workflow.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 | $0.00033 | $0.00804 |
| Opus 5 | $0.00016 | $0.00402 |
| Sonnet 5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
Git Workflow 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 4d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Skill
Cuándo usar esta skill
- Cuando necesites actualizar el CHANGELOG.md con nuevos cambios.
- Cuando vayas a hacer commit de cambios al repositorio.
- Cuando necesites hacer push de cambios al remoto.
- Cuando prepares una nueva release.
Convenciones de Commits
Este proyecto usa Conventional Commits:
type(scope): description
Tipos válidos:
| Tipo | Uso |
|---|---|
feat |
Nueva funcionalidad |
fix |
Corrección de bugs |
docs |
Cambios en documentación |
style |
Formato (sin cambio de código) |
refactor |
Refactorización |
test |
Añadir/modificar tests |
chore |
Mantenimiento |
Ejemplos:
feat(semantic): add image caption indexing
fix(navigation): resolve path validation error
docs: update tool reference with new parameters
Flujo de Trabajo Completo
1. Verificar estado actual
# Ver estado de archivos
git status
# Ver historial reciente
git log --oneline -10
2. Actualizar CHANGELOG.md
Formato requerido (Keep a Changelog):
## [Unreleased]
### Added
- Nueva feature X que hace Y.
### Changed
- Modificación en Z.
### Fixed
- Corrección del bug en W.
Secciones válidas: Added, Changed, Deprecated, Removed, Fixed, Security
3. Realizar commit
# Añadir todos los cambios
git add .
# Commit con mensaje convencional
git commit -m "type(scope): descripción"
Trailers especiales:
- Para bugs reportados:
git commit --trailer "Reported-by:<name>" - Para issues:
git commit --trailer "Github-Issue:#<number>"
⚠️ NUNCA incluir
Co-Authored-Byen los commits.
4. Push al remoto
git push origin main
Proceso de Release
Para crear una nueva versión:
1. Mover cambios de Unreleased a una versión
## [1.2.0] - 2026-01-20
### Added
- (mover items de Unreleased)
2. Actualizar versión en pyproject.toml
[project]
version = "1.2.0"
3. Commit de release
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.
- 4d ago First seen · 151 lines · 33 tokens per session scan A 6fb952b01246
Git Workflow is a skill published in the GitHub repository Vasallo94/obsidian-mcp-server (9 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 804 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-31.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.