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/jatingargiitk/evoagents/perceptionnpx skills add jatingargiitk/evoagents --skill perceptiongit clone --depth 1 https://github.com/jatingargiitk/evoagentsWrote 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/jatingargiitk/evoagents/perception)<a href="https://agentmods.dev/skills/jatingargiitk/evoagents/perception"><img src="https://agentmods.dev/badge/skills/jatingargiitk/evoagents/perception.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.00015 | $0.00430 |
| Opus 5 | $0.00008 | $0.00215 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
perception 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- perception — 89% identical, 16 lines differ
What it actually says
Perception Skill
Analyze the user's question and extract structured information for downstream planning.
When to Use
USE this skill when:
- A new user question arrives and needs to be analyzed
- Downstream skills need structured context about the query
When NOT to Use
DON'T use this skill when:
- The question has already been analyzed by a prior perception pass
Constraints
- MUST output valid JSON matching the Output Format schema
- MUST identify all key entities and topics in the question
- NEVER include speculation about the answer — only analyze the question itself
Output Format
Respond with ONLY a JSON object:
{
"intent": "What the user wants to know (1 sentence)",
"entities": ["key entities", "topics", "concepts"],
"constraints": ["time range", "domain", "format constraints"],
"recency_required": true,
"complexity": "simple | moderate | complex"
}
Examples
Query: "What happened in AI this week?" Expected output:
{
"intent": "Find recent AI news and developments from the past week",
"entities": ["artificial intelligence", "AI news"],
"constraints": ["time range: past week"],
"recency_required": true,
"complexity": "moderate"
}
Query: "Explain how gradient descent works" Expected output:
{
"intent": "Explain the gradient descent optimization algorithm",
"entities": ["gradient descent", "optimization", "machine learning"],
"constraints": [],
"recency_required": false,
"complexity": "moderate"
}
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 · 77 lines · 15 tokens per session scan A 9901346d3e3a
perception is a skill published in the GitHub repository jatingargiitk/evoagents (2 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 430 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…