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/layer1labs/specsmith/ollama-integrationnpx skills add layer1labs/specsmith --skill ollama-integrationgit clone --depth 1 https://github.com/layer1labs/specsmithWrote 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/layer1labs/specsmith/ollama-integration)<a href="https://agentmods.dev/skills/layer1labs/specsmith/ollama-integration"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/ollama-integration.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.00020 | $0.00371 |
| Opus 5 | $0.00010 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
ollama-integration 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.
What it actually says
Ollama Platform Integration
This skill enables specsmith projects to integrate with Ollama for local AI model serving while maintaining governance compliance.
Requirements Covered
- REQ-112: Ollama Platform Integration
- Allows specsmith projects to integrate with Ollama for local AI model serving with human approval
Integration Capabilities
Platform Features
- Ollama model management and deployment
- Local model serving
- GPU and CPU resource utilization
- API endpoint configuration for Ollama services
- Model pulling and caching
Governance Requirements
- Human approval required for all Ollama integrations
- Configuration management with governance controls
- Security best practices enforcement
- Resource monitoring and logging
Usage Examples
# Initialize Ollama integration
specsmith skill install ollama-integration
# Configure Ollama platform settings
specsmith ollama configure --platform ollama --model-path /path/to/models --gpu-enabled true
# Pull and run model via Ollama
specsmith ollama run --model llama3 --port 11434
Configuration
The skill requires the following configuration in scaffold.yml:
ollama:
platform: ollama
model_path: /path/to/models
gpu_enabled: true
port: 11434
model_name: "llama3"
Security Considerations
- All Ollama integrations require human approval
- Local model access controls must be configured
- Network security must be enforced
- Resource usage monitoring is required
Compliance Requirements
- Follow security best practices for AI platform integrations
- Maintain audit logs of all Ollama interactions
- Ensure proper resource management and monitoring
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 · 68 lines · 20 tokens per session scan A da6ff2055532
ollama-integration is a skill published in the GitHub repository layer1labs/specsmith (7 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 371 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-08-31.
Other skills, from other repositories
arch-audit
Audit Claude Code architecture files against Anthropic docs and release notes, and verify internal ecosystem consistency. Run on demand to maintain compliance, catch new features, and keep the context system clean.
skill-dev
Code quality audit: detect cross-module coupling, N+1 queries, dead exports, antipatterns, over-large components. Cross-checks against refactoring backlog.
accessibility-audit
Unified accessibility audit - axe-core WCAG 2.2 scan, APCA contrast measurement, static a11y checks (aria-label, tabindex, form labels, focus visibility, onClick on non-interactive). Static and live modes.
pr-review
Autonomous local code review. Reviews either an open PR's diff (via gh) or the local working diff against a base branch (--local, auto-selected when no PR exists yet), spawns a dedicated review subagent with universal + stack-specific severity criteria, posts the review as a comment on the PR (audit trail; skipped in…
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.
security-audit
Security audit: auth/authz on API routes, input validation, row-level access control (RLS in Postgres, ORM scopes or app-level guards elsewhere), response shape review, secret exposure, HTTP headers. Native mode checks entitlements and Keychain. MCP-aware (v1.20+): when mcp-nvd server is wired, Step 3c queries live…