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 jezweb/vite-flare-starter --skill agent-asks-tasksgit clone --depth 1 https://github.com/jezweb/vite-flare-starterWrote 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/jezweb/vite-flare-starter/agent-asks-tasks)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/agent-asks-tasks"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/agent-asks-tasks.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00756 |
| Opus 5 | $0.00032 | $0.00378 |
| Sonnet 5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
agent-asks-tasks 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent asks + tasks — durable commitments
Long-running agents lose context when sessions compact or routines fire days apart. Anything you commit to in mid-conversation that isn't immediately resolved should be written down — otherwise it silently disappears.
This skill uses the existing entities store with two types:
type: "ask"— a question YOU owe the user (waiting on their answer)type: "task"— a deliverable YOU owe yourself (you'll do it)
When to write an ask
You realise you need information from the user to proceed, but they haven't given it yet. Examples:
- "I need Jez's preferred timezone for these reports"
- "What's the deadline on the Q3 OKRs?"
- "Should the email go to the team alias or just to Sarah?"
Don't write asks for trivia (date format, single-word clarifications) — those should be inline in the same response.
entity_create({
type: "ask",
title: "Confirm Q3 OKRs deadline",
status: "open",
fields: { body: "Need Jez's hard deadline for Q3 OKRs draft." }
})
When to write a task
You committed to do something later, OR a routine surfaced something that needs follow-through but isn't blocking the current turn. Examples:
- "I'll review the 3 PDFs Jez uploaded by tomorrow"
- "Check whether Gmail OAuth is still authorised before next sweep"
- "Draft the marketing brief once research is in"
entity_create({
type: "task",
title: "Review 3 uploaded PDFs",
status: "open",
fields: { body: "Summarise each, surface findings.", dueAt: "2026-05-08" }
})
When to close
When the answer arrives (ask) or the work is done (task), close the entity:
entity_update({ id: "<entity_id>", status: "closed" })
Optionally store the answer or outcome in fields.resolution.
Reading what's open
Before answering when you might have unfinished business, check:
entity_search({ type: "ask", status: "open" })
entity_search({ type: "task", status: "open" })
If anything is open and relevant, mention it: "By the way, I'm still waiting on your answer about X — should I proceed without it?"
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 First seen · 95 lines · 63 tokens per session scan A f4aa17ef0743
agent-asks-tasks is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 13d ago), licensed MIT. It adds 63 tokens to every session and 756 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-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.