Borrowing it
Nothing to install: this file belongs to zkysar1/Claude-Mind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zkysar1/Claude-Mind/main/.claude/skills/aspirations-evolve/SKILL.mdgit clone --depth 1 https://github.com/zkysar1/Claude-MindWrote 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/zkysar1/claude-mind/aspirations-evolve)<a href="https://agentmods.dev/skills/zkysar1/claude-mind/aspirations-evolve"><img src="https://agentmods.dev/badge/skills/zkysar1/claude-mind/aspirations-evolve/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/zkysar1/claude-mind/aspirations-evolve"><img src="https://agentmods.dev/badge/skills/zkysar1/claude-mind/aspirations-evolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Prompt Injection · line 1103 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00095 | $0.21431 |
| Opus 5 | $0.00048 | $0.10716 |
| Sonnet 5 | $0.00019 | $0.04286 |
| Haiku 4.5 | $0.00010 | $0.02143 |
Grade A, and why
aspirations-evolve 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 6d 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 — 1,324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolution Engine (evolve sub-command)
Trigger evolution check — the system evaluates its own strategy and generates new aspirations. Invoked by Phase 9 performance-based evolution triggers, or directly via /aspirations evolve. Covers developmental stage assessment, config parameter tuning, state reading, evolve-first aspiration review, constraint-aware rebalancing, self-driven gap analysis, novelty filter, cap enforcement, logging, profile/meta update, forge check, pattern signature calibration, and strategy archive.
Step 0: Load Conventions — Bash: load-conventions.sh with each name from the conventions: front matter. Read only the paths returned (files not yet in context). If output is empty, all conventions already loaded — proceed to next step.
evolve
Trigger evolution check — the system evaluates its own strategy and generates new aspirations:
- Developmental Stage Assessment (competence-based):
Read core/config/developmental-stage.yaml (stage definitions, competence_mapping) Read agents/<agent>/developmental-stage.yaml (current assessment, epsilon, schema log) old_stage = agents/<agent>/developmental-stage.yaml.overall_stage old_highest = agents/<agent>/developmental-stage.yaml.current_assessment.highest_capability # Stage-block computation is SCRIPT-ENFORCED (g-115-2624). The former inline # formula here (tree-leaf capability mean at depth >= 2, competence_mapping # EXPLORE=0.15/CALIBRATE=0.45/EXPLOIT=0.70/MASTER=0.90, stage bands # 0.30/0.55/0.80, exploration_budget = clamp(1 - tree_maturity, 0.15, 0.85)) # now lives in core/scripts/_competence.py::assess_stage — the SAME math, # deterministic and refreshed at every curriculum-evaluate chokepoint too. # WHY: LLM-discretionary producers drift silent (rb-3171); this exact block # fired once in 2 months on zeta, pinning ZDS agents at 'exploring' with # forge gated and resolved_hypotheses contradicting its own sibling # evidence (ZDS omni code-read 2026-07-18). The one call below computes AND # writes: overall_stage, current_assessment.{stage,tree_maturity, # highest_capability,lowest_capability,exploration_budget, # resolved_hypotheses(=pipeline_resolved),average_competence,components, # evidence,producer,assessed_at}, exploration.epsilon. Do NOT re-inline the # math here. Bash: py -3 core/scripts/competence-assess.py Parse JSON stdout → stage_assessment.{stage, tree_maturity, highest_capability, exploration_budget} If stage_assessment.highest_capability != old_highest: Log: "DEVELOPMENTAL UPDATE: highest_capability → {stage_assessment.highest_capability}" If stage_assessment.stage != old_stage: # Numbers are already written by the script; the LLM applies the # stage-definition SIDE EFFECTS (behavioral envelope from # core/config/developmental-stage.yaml stages.<stage>.behaviors): Update allowed hypothesis_types and max_commitment (per stage definition) Log: "DEVELOPMENTAL TRANSITION: {old_stage} → {stage_assessment.stage}" Metacognitive self-check (every 5th goal via sq-010): "Based on my knowledge, accuracy, and experience — what capability level am I at? Does it match the computed level?" If divergence: log as ACCOMMODATION in schema_operations.log Schema operation detection: Read recent reflections and violations For each finding that contradicts existing framework: Log as ACCOMMODATION in schema_operations.log Set equilibration_state = "disequilibrium" For each finding that confirms existing framework: Log as ASSIMILATION in schema_operations.log Update agents/<agent>/developmental-stage.yaml: schema_operations.log + equilibration_state ONLY (from the two blocks above). # ALL numeric assessment fields (overall_stage, current_assessment.*, # exploration.epsilon) are script-written by competence-assess.py — the # single producer since g-115-2624. Evolve MUST NOT hand-write any of # them; hand-writing re-creates the g-115-2028 last-writer-wins collision # AND the rb-3171 silent-drift class this delegation eliminated. Evolve's # write surface here is the schema_operations narrative alone. Run active forgetting pruning: Read core/config/memory-pipeline.yaml forgetting config For each leaf node, calculate retention score If retention < 0.4: archive (if validated) or deprecate
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.
- 6d ago Changed · +12 lines 8ae9978bf04a
- 9d ago First seen · 1,312 lines · 95 tokens per session scan A d6d56115d06e
aspirations-evolve is a skill published in the GitHub repository zkysar1/Claude-Mind (5 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 21,431 once invoked, about $0.0005 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
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.worker-delegation
Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.writing-hive-skills
Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories). Use when the user asks to create, scaffold, add, or package a new skill for a Hive agent.