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 ChronoAIProject/NyxID --skill aevatar-schedulergit clone --depth 1 https://github.com/ChronoAIProject/NyxIDWrote 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/chronoaiproject/nyxid/aevatar-scheduler)<a href="https://agentmods.dev/skills/chronoaiproject/nyxid/aevatar-scheduler"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/aevatar-scheduler/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/chronoaiproject/nyxid/aevatar-scheduler"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/aevatar-scheduler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
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 →
- high Privilege Escalation · line 333 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 365 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 135 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 Rogue Agent · line 218 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00089 | $0.07073 |
| Opus 5 | $0.00044 | $0.03537 |
| Sonnet 5 | $0.00018 | $0.01415 |
| Haiku 4.5 | $0.00009 | $0.00707 |
Grade A, and why
aevatar-scheduler scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# token. A raw curl to the aevatar backend with ~/.nyxid/access_token resolves NO scope How it starts
The opening of the file, as written. The whole thing — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule an Aevatar service on a cron
Route to the right resource FIRST — three paths, not one
"Run it on a schedule" is three different resources with three different owners, credentials, and APIs. Pick before you call anything; using the wrong one is not a shortcut, it is the wrong resource.
| The user wants to schedule… | Resource owner | Canonical entry | Credential |
|---|---|---|---|
| An already-bound Studio Team member workflow | scope → team → member |
aevatar_schedule_member_workflow, or REST /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations |
Dedicated Agent Key |
| An independent scheduled Ornn skill agent or a one-shot reminder | Scheduled agent / catalog actors | scheduled_agent_creator, then agent_builder — see aevatar-automation |
Dedicated Agent Key |
| A typed service invocation | Generic platform schedule actor | Generic /api/schedules — the rest of this skill |
Typed source; may be a NyxID binding exchange |
If the owner is a Team member, the canonical path is the member automation route — not generic
/api/schedules. Generic /api/schedules is a platform-level resource for typed service invocations. It
is supported, but it is not a fallback for Team member automation, and reaching for it because
you already know its shape is the most common mistake here.
Never convert between identities by route position, prefix, equality, or a familiar-looking string:
memberId, draft workflowId, publishedServiceId, UserService ID, catalog service ID, schedule
ID, and Agent Key ID are seven distinct things.
Studio Team member automation (the canonical member path)
Use aevatar_schedule_member_workflow in-session, or the owner-scoped REST route. The owner is the
exact scopeId + teamId + memberId tuple; teamId is a containment guard. The server reads the
member summary and derives publishedServiceId — you never substitute a draft workflowId, a
service ID, a binding ID, a route, a model, or a credential ID for 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.
- 9d ago First seen · 486 lines · 89 tokens per session scan A f0f3f4f6a0e6
aevatar-scheduler is a skill published in the GitHub repository ChronoAIProject/NyxID (36 stars, last pushed today), licensed Apache-2.0. It adds 89 tokens to every session and 7,073 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
external-lib-flow
Workflow for onboarding an external private library so AI can use it without source access.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
adhoc-flow
Workflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.
coding-agents-prompting-flow
Workflow for authoring and adapting AI-agent prompts: skills, agents, workflows, rules, etc.
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…
anyr
Use when reading, searching, creating, or updating Anytype documents (objects, spaces, types, properties, files, chats) from the command line with the configured anyr CLI, including JSON output patterns for scripting.