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 agents/taipt1504/agent-skills/slice-executorgit clone --depth 1 https://github.com/taipt1504/agent-skillsWrote 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/agents/taipt1504/agent-skills/slice-executor)<a href="https://agentmods.dev/agents/taipt1504/agent-skills/slice-executor"><img src="https://agentmods.dev/badge/agents/taipt1504/agent-skills/slice-executor.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.00059 | $0.03150 |
| Opus 5 | $0.00030 | $0.01575 |
| Sonnet 5 | $0.00012 | $0.00630 |
| Haiku 4.5 | $0.00006 | $0.00315 |
Grade A, and why
slice-executor 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 3d 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.
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.
- 3d ago First seen · 299 lines · 59 tokens per session scan A 37c740e51077
slice-executor is an agent published in the GitHub repository taipt1504/agent-skills (4 stars, last pushed 3mo ago), with no licence file. It adds 59 tokens to every session and 3,150 once invoked, about $0.0003 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 agents, from other repositories
java-reviewer
Review Java code changes against OpenMetadata backend patterns and Kafka-grade quality standards — method size limits, IntelliJ-level inspections, immutability, granular error handling, and human-readable code.
spring-ai-expert
Use this agent when the user asks questions about Spring AI framework, its features, configuration, usage patterns, API methods, integration approaches, or troubleshooting. Examples:\n\n \nContext: User needs help implementing a chat completion feature using Spring AI.\nuser: "How do I set up a chat client with Spring…
scout neqsim capabilities
Analyzes engineering tasks to identify required capabilities (physics, chemistry, process, economics), checks NeqSim's existing coverage, identifies gaps, plans implementations, and recommends skills to load. Use before starting any complex engineering task to ensure all needed tools and models are available.
extract process to neqsim json
Extracts process simulation data from unstructured input (text descriptions, PFDs, operating data, tables, data sheets) and converts it into running NeqSim simulations. Small/medium processes use the JSON builder (ProcessSystem.fromJsonAndRun). Large multi-area processes are split into multiple ProcessSystems composed…
make a neqsim process simulation
Creates an executable NeqSim process simulation from an engineering description. Builds thermodynamic fluids, assembles flowsheets with ProcessSystem, runs the simulation, validates results, and can evaluate P&ID-derived valve/action scenarios through neqsim.process.operations or MCP runOperationalStudy. Supports…
create a neqsim jupyter notebook
Creates Jupyter notebook examples demonstrating NeqSim capabilities — process simulations, thermodynamic calculations, PVT studies, and engineering workflows. Uses devtools workspace class imports for task notebooks, with proper structured markdown cells and visualization.