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/avinava/sf-documentation-knowledge/maps-developer-guidenpx skills add Avinava/sf-documentation-knowledge --skill maps-developer-guidegit clone --depth 1 https://github.com/Avinava/sf-documentation-knowledgeWrote 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/avinava/sf-documentation-knowledge/maps-developer-guide)<a href="https://agentmods.dev/skills/avinava/sf-documentation-knowledge/maps-developer-guide"><img src="https://agentmods.dev/badge/skills/avinava/sf-documentation-knowledge/maps-developer-guide.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.00021 | $0.00201 |
| Opus 5 | $0.00010 | $0.00101 |
| Sonnet 5 | $0.00004 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
sf-knowledge-maps-developer-guide 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 21 lines · 21 tokens per session scan A 731e9a390348
sf-knowledge-maps-developer-guide is a skill published in the GitHub repository Avinava/sf-documentation-knowledge (1 stars, last pushed 1mo ago), with no licence file. It adds 21 tokens to every session and 201 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
edit-model-code
Coding-discipline guidelines for surgically modifying model code inside a per-experiment fork in the autoresearch loop. Adapts Andrej Karpathy's LLM-coding guidelines (think before coding, simplicity first, surgical changes, goal-driven execution) to this project's invariants — no semantics drift, one mechanism per…
matryca-python-standards
Apply Matryca Python 3.12+, uv, typing, validation, concurrency, filesystem-safety, logging, and verification standards. Use whenever creating or modifying Python source or tests.
python-mcp-server-expert
Expert assistant for developing Model Context Protocol (MCP) servers in Python using FastMCP, mcp package, Pydantic, and async patterns. Use when building MCP tools, resources, prompts, or debugging Python MCP server issues.
python-testing-patterns
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.