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-feasibility-advisorgit 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-feasibility-advisor)<a href="https://agentmods.dev/skills/chronoaiproject/nyxid/aevatar-feasibility-advisor"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/aevatar-feasibility-advisor/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-feasibility-advisor"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/aevatar-feasibility-advisor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 100 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 114 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 197 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.00138 | $0.06162 |
| Opus 5.5 | $0.00055 | $0.02465 |
| Sonnet 5.5 | $0.00028 | $0.01232 |
| Haiku 4.5 | $0.00014 | $0.00616 |
Grade A, and why
aevatar-feasibility-advisor 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 2mo 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aevatar feasibility advisor
Before you (or the user) commit to building something on Aevatar, answer three questions
honestly: Is it possible? What must be in place first? If not, why — and what's the
alternative? This skill exists so you negotiate scope up front instead of discovering a
hard blocker halfway through. It only advises — once a plan is feasible, hand off to
aevatar-workflow-authoring → aevatar-team-builder → aevatar-service-publisher →
aevatar-scheduler, or to aevatar-agent-profile-management for the Agent Profile surface
(see aevatar-platform-map). For codex_exec, choose the target here, then hand setup or
repair to aevatar-codex-exec-node-setup, require the public
aevatar-codex-exec-workflow-sample proof, and only then author the real workflow.
Three different reasons a thing can be unavailable — never blur them
They have different owners and different fixes. Collapsing them into "it's host-gated" is the most common wrong answer here.
| Reason | What it looks like | Who fixes it |
|---|---|---|
| Not connected | The connector is in /api/v1/catalog but missing from authoritative /api/v1/keys |
The user, self-serve |
| Host-gated | The capability is deployed and works, but a host policy governs one aspect (NyxID external exposure; Agent Profile rollout admission) | The host — not you, not the user |
| Not deployed | The capability's whole API surface is absent from the running build | The host, by deploying a build that exposes it |
"Not deployed" is the one people get wrong most: the feature exists in the codebase and in design
docs, so it sounds available. Probe the live surface, never a branch or a memory —
GET /api/openapi.json and check whether the complete route family is advertised.
Agent Profile management is an owner-managed capability — an authenticated user manages their
own profile; it is not host-only configuration. It remains deployment-gated, so probe the live
GET /api/openapi.json and require the complete agent-profiles route family before mutation.
Do not preserve a historical claim that production lacks or exposes it; the live OpenAPI is the
only answer for the current deployment.
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.
- 2mo ago First seen · 287 lines · 138 tokens per session scan A d1bc9cd1badc
aevatar-feasibility-advisor is a skill published in the GitHub repository ChronoAIProject/NyxID (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 138 tokens to every session and 6,162 once invoked, about $0.0006 per session on Opus 5.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.
aevatar-feasibility-advisor compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| aevatar-feasibility-advisorChronoAIProject/NyxID | Skill | 41 | yesterday | Apache-2.0 | A | 138 | Claude Code |
| opik-diagnosecomet-ml/opik-mcp | Skill | 225 | 9d ago | Apache-2.0 | A | 187 | Claude Code |
| ue-mcp-epic-routingdb-lyon/ue-mcp | Skill | 476 | yesterday | MIT | A | 81 | Claude Code, Codex |
| qa-knowledgegriddynamics/rosetta | Skill | 370 | yesterday | Apache-2.0 | A | 32 | Claude Code, Codex |
| apitapn1byn1kt/apitap | Skill | 131 | 17d ago | Apache-2.0 | A | 0 | Claude Code, Codex |
| frontmcp-setupagentfront/frontmcp | Skill | 148 | yesterday | Apache-2.0 | A | 176 | Claude Code, Codex |
| x-use-reviewihuzaifashoukat/x-use | Skill | 181 | 4d ago | MIT | A | 56 | Claude Code |