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 seekayel/claude-plugins --skill veris-api-skillgit clone --depth 1 https://github.com/seekayel/claude-pluginsWrote 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/seekayel/claude-plugins/veris-api-skill)<a href="https://agentmods.dev/skills/seekayel/claude-plugins/veris-api-skill"><img src="https://agentmods.dev/badge/skills/seekayel/claude-plugins/veris-api-skill/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/seekayel/claude-plugins/veris-api-skill"><img src="https://agentmods.dev/badge/skills/seekayel/claude-plugins/veris-api-skill.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.00056 | $0.00538 |
| Opus 5.5 | $0.00022 | $0.00215 |
| Sonnet 5.5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
Veris API 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 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.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Veris API Skill
This skill provides comprehensive access to the Veris AI agent simulation and evaluation platform (https://simulator.api.veris.ai/).
When to Use This Skill
Use this skill when you need to:
- Create and manage AI agents for testing
- Generate simulation scenarios and scenario sets
- Run agent simulations in controlled environments
- Evaluate agent performance with various grading approaches
- Set up and manage API keys for the Veris platform
API Capabilities
Authentication
- Create and manage API keys
- Support for service and general API key types
- Secure key-based authentication via X-API-Key header
Agent Management
- Create new AI agent configurations
- List and retrieve existing agents
- Update agent specifications
- Version control for agent configurations
Scenario Generation
- Generate scenario "bones" (variation dimensions)
- Create comprehensive scenario sets
- Add, update, and delete individual scenarios
- Configure scenario dimensions and parameters
Simulation Execution
- Create and run simulation sessions
- Monitor simulation progress and status
- Kill running simulations when needed
- Retrieve simulation metadata and results
Evaluation Framework
- Create evaluation runs for agent assessment
- Support multiple grading approaches:
- Python-based custom graders
- LLM score model graders
- Multi-grader composition systems
- Retrieve detailed evaluation results and metrics
Usage Examples
When a user requests any of the following, this skill should be used:
- Agent Development: "Create an AI agent for customer support simulation"
- Scenario Testing: "Generate test scenarios for my chatbot"
- Performance Evaluation: "Run simulations to evaluate my agent's performance"
- API Management: "Set up API access for the Veris platform"
API Base URL
https://simulator.api.veris.ai
Authentication Requirements
All API calls require an X-API-Key header with a valid Veris API key. Users must either:
- Set VERIS_API_KEY environment variable
- Provide API key directly in commands
- Create API keys using the /api-keys endpoints
What ships with it
1 file 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.
- 6d ago First seen · 74 lines · 56 tokens per session scan A 98d918a80d0b
Veris API is a skill published in the GitHub repository seekayel/claude-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 538 once invoked, about $0.0002 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-13.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.