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 skills add queelius/claude-anvil --skill vistagit clone --depth 1 https://github.com/queelius/claude-anvilWrote 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/queelius/claude-anvil/vista)<a href="https://agentmods.dev/skills/queelius/claude-anvil/vista"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/vista/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/queelius/claude-anvil/vista"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/vista.svg" alt="Reviewed on agentmods" width="80" 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.00127 | $0.01667 |
| Opus 5.5 | $0.00051 | $0.00667 |
| Sonnet 5.5 | $0.00025 | $0.00333 |
| Haiku 4.5 | $0.00013 | $0.00167 |
Grade A, and why
vista 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 8d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vista
Vista surfaces salient research directions by reading the Future Work, Limitations, Discussion, and Conclusion sections of highly-cited papers. The MCP server does the mechanical work (OpenAlex search, PDF fetch, section extraction, caching). This skill tells you when to call which MCP tool and how to synthesize the structured payload it returns.
Core principle
The MCP tools are mechanical. They return raw section text plus metadata. You (Claude in this conversation) read the sections and produce the synthesis: ranking, pattern detection, novelty assessment, cross-paper themes. Do not expect the MCP to "give you the answer"; it gives you the inputs.
When to invoke which tool
Read the user's question carefully and route:
| User intent | Tool | Notes |
|---|---|---|
| "Open problems / future work / research directions in a topic" | topic_followups(topic, max_papers=8, year_min=2020, min_citations=30) |
Most common. Recent, highly-cited, arXiv-available. |
| "What does paper / arXiv:1234.5678 / DOI X say about future work?" | paper_followups(identifier) |
Single-paper deep-dive. Identifier can be DOI, arXiv id, OpenAlex id, or title. |
| "Older / classical / under-explored / neglected directions in X" | find_seminal(topic, year_max=2019, min_citations=1000) |
Legacy track. The "papers everyone cites but nobody followed up on." |
| "Broad / cross-field / serendipitous search; find directions outside my prior work" | broad_followups(query, fields=None, max_papers=12) |
Exploratory; looser thresholds; spans fields. |
| "Search the local catalog of distilled directions" | search_directions(query, ...) |
Use after a build run. Searches what the user has already mined. |
| "List interesting / open / started directions" | list_directions(...) |
Curation/review. |
| "Mark this direction as interesting" | mark_direction(direction_id, status, notes) |
User curation. |
| "Save these directions for paper X" | submit_directions(paper_id, directions) |
After you've synthesized directions, persist them so future runs can search them. Appends by default; curation is never lost. |
| "What papers / directions / fields are in the store?" | status() or run_sql(...) |
Inspection. |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago Changed · -16 lines 2ab9d5167ada
- 11d ago First seen · 137 lines · 127 tokens per session scan A bfe7a52896ae
vista is a skill published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 9d ago), licensed MIT. It adds 127 tokens to every session and 1,667 once invoked, about $0.0005 per session on Opus 5.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-10-19.
Other skills, from other repositories
karpenter
Design, install, debug, review, plan capacity, audit scaling history, migrate from Cluster Autoscaler, and upgrade Karpenter v1.x on EKS. Covers NodePool, EC2NodeClass, NodeClaim, Spot diversity, disruption strategy, Pod Identity/IRSA, interruption queue, private clusters, AMI rotation, and GitOps integration. Use…
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
azure
Azure identity (Workload Identity, OIDC, Entra ID), resource tagging, AKS platform patterns, RBAC scoping, and production-readiness review — with Terraform generation.
kubescape
Check Kubernetes manifests, Helm charts, Kustomize overlays and live clusters against NSA-CISA, MITRE ATT&CK, CIS (EKS, AKS, GKE, vanilla) and SOC2 with the Kubescape CLI. Covers framework choice, score and severity gates, PR gates that fail only on new findings (--baseline), exceptions that actually suppress…
chaos
Design, run, and debug Chaos Engineering experiments on Kubernetes using Litmus Chaos v3 and Chaos Mesh v2. Covers fault injection (pod-delete, network-loss, CPU stress, node-drain), steady-state hypothesis probes, GameDay runbooks, scheduled experiments, DORA feedback loop, and RBAC setup. Use when asked to "inject a…
opa
Generate, test, validate, explain, and debug OPA (Open Policy Agent) Rego policies and Conftest configurations. Covers deny/warn/violation rules, unit tests, regal linting, conftest fmt, namespace design, input shape analysis, and GitHub Actions integration. Use when asked to "write a policy", "test a rego file"…