QwenPaw is a personal AI assistant that runs on a local machine or in the cloud and connects to multiple chat applications. It provides memory, file workspaces, multiple agents, skills, plugins, and integrations with language-model providers and external tools. The catalogue entries are skills that extend its capabilities.
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 agentscope-ai/QwenPaw --skill cron-engit clone --depth 1 https://github.com/agentscope-ai/QwenPawWrote 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/agentscope-ai/qwenpaw/cron-en)<a href="https://agentmods.dev/skills/agentscope-ai/qwenpaw/cron-en"><img src="https://agentmods.dev/badge/skills/agentscope-ai/qwenpaw/cron-en/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/agentscope-ai/qwenpaw/cron-en"><img src="https://agentmods.dev/badge/skills/agentscope-ai/qwenpaw/cron-en.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 14 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 249 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00039 | $0.02367 |
| Opus 5 | $0.00019 | $0.01184 |
| Sonnet 5 | $0.00008 | $0.00473 |
| Haiku 4.5 | $0.00004 | $0.00237 |
Grade A, and why
cron 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 11d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron (Scheduled Task Management)
When to Use
Use this skill only when you need to automatically execute something at a future time or repeat execution on a schedule.
Should Use
- User asks to do something "daily / weekly / hourly"
- User asks for automatic reminders or execution "tomorrow at 9 AM / next Monday / at a specific time"
- Long-term periodic notifications, checks, or reports are needed
Should Not Use
- The task only needs to be executed once right now
- It is just a normal reply within the current session
- The user has not specified an execution time or schedule
- The target channel / user / session is still unclear
Decision Rules
- Only use cron for future scheduled or periodic execution
- If it only needs to be done once immediately, do not create a cron job
- Before creating, confirm execution time/schedule, target channel, target-user, and target-session
- All cron commands must explicitly include
--agent-id - Do not rely on the default agent, or the task may end up in the default workspace
- For an agent task that should run without channel output, add
--silent; execution, session history, trace, and optional Inbox recording still continue
Hard Rules
Must Explicitly Specify --agent-id
All qwenpaw cron commands must include:
--agent-id <your_agent_id>
Your agent_id is found in the Agent Identity section of the system prompt (Your agent id is ...). Do not omit it, or the task may be incorrectly created in the default agent's workspace.
Common Commands
# List tasks
qwenpaw cron list --agent-id <agent_id>
# View task details
qwenpaw cron get <job_id> --agent-id <agent_id>
# View task status
qwenpaw cron state <job_id> --agent-id <agent_id>
# Create a task
qwenpaw cron create --agent-id <agent_id> ...
# Delete a task
qwenpaw cron delete <job_id> --agent-id <agent_id>
# Pause / Resume a task
qwenpaw cron pause <job_id> --agent-id <agent_id>
qwenpaw cron resume <job_id> --agent-id <agent_id>
# Run an existing task once immediately
qwenpaw cron run <job_id> --agent-id <agent_id>
# Update an existing task
qwenpaw cron update <job_id> --agent-id <agent_id> ...
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.
- 11d ago First seen · 286 lines · 39 tokens per session scan A 1bd62e169ba7
cron is a skill published in the GitHub repository agentscope-ai/QwenPaw (34,741 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 2,367 once invoked, about $0.0002 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
cron-task-creator
Create, manage, and run scheduled automated tasks (cron jobs) in Clacky. Use this skill whenever the user wants to create a new automated task or cron job, set up recurring automation, schedule something to run daily/weekly/hourly, view all scheduled tasks, edit an existing task prompt or cron schedule, enable or…
meeting-summarizer
Summarize a completed meeting from its transcript. Produces a structured summary with key decisions, action items, and discussion highlights. Triggered automatically when a meeting ends.
yida-create-process
A tool for creating a new Yida approval form and configuring its workflow. An approval workflow routes submitted form data through defined review steps before it is completed.
yida-logout
A logout and account-management procedure for YiDa, a platform for building and running business applications. It distinguishes disconnecting the current project from deleting shared login profiles.
post-dev-recap
Post-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (use /tech-brief)…
obsidian-cli
Obsidian vault integration via official CLI. Use when: capturing dev artifacts to Obsidian vault, searching vault for context, appending to daily note, managing tasks in vault. Not for: general note-taking without Obsidian (use regular files), browsing Obsidian docs (use agent-browser). Output: vault search results…