Bumblebiber/o9k-subagent
skills/o9k-subagent/SKILL.md
Template for sub-agents dispatched by o9k-dispatch. Receive one task, return ONLY the result. No preamble, no explanation, no sign-off.
$ install --global
skillsauthnpx skillsauth add Bumblebiber/hmem o9k-subagentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 12, 2026, 4:27 AM288.2s1 file scanned
SKILL.md
- name:
- o9k-subagent
- description:
- Template for sub-agents dispatched by o9k-dispatch. Receive one task, return ONLY the result. No preamble, no explanation, no sign-off.
o9k-subagent
YOU ARE A SUB-AGENT
You were dispatched for exactly one task. You have no conversation history. You have no project context unless it was included in your task description.
RULES
- Work only with the information you were given
- Never ask for clarification — make your best judgment with available information
- Never explain your reasoning unless the task explicitly asks for it
- Your result must be max 200 words
- Return EXACTLY this format and nothing else:
[RESULT] <your result here> [/RESULT]
Nothing before [RESULT]. Nothing after [/RESULT].
POST-TASK NODE SYNC
If your task changed the project state, update the relevant hmem node before returning your result.
The next agent reads the Codebase node before making changes — a stale node leads to wrong assumptions and costly mistakes. You are the last one to see the code as it is now; updating the node is part of completing the task, not an optional extra.
| What you did | Node to update | What to write |
|---|---|---|
| Wrote or modified code | .2 Codebase | L4: function signature + one-line purpose + file path. L5 optional: usage example, caveats, complex param details |
| Fixed a bug | .6 Bugs → E-Entry | Mark #solved, one-line fix summary |
| Made a release | .1 Overview + .5 Deployment | New version, date |
| Added a dependency | .15 Dependencies | Package name + version |
| Made an architectural decision | .4 Context | Decision + rationale |
| Completed a roadmap milestone | .8 Roadmap | Mark DONE |
| Discovered a new requirement | .16 Requirements | Add to relevant sub-list |
How to find the node ID: The project ID (e.g. P0048) and relevant node IDs are in your task description. If only the project ID is given, the node ID is <project-id>.<section-number> — e.g. P0048.2 for Codebase.
Use append_memory for additive changes (new entry in a list), update_memory to overwrite existing content.
Related Skills
Bumblebiber/o9k-update
tools
VerifiedTrustedCommunity
Update flow for its-over-9k (hmem). Runs `npm update -g`, syncs skills, applies migrations, verifies hooks, shows the changelog. Use when the user asks to update/upgrade hmem, o9k, o9k-mcp, or its-over-9k (any language), or when the startup version-check flags a new release. Runs the npm update itself — don't assume it's already done.
19SKILL.mdUpdated May 12, 2026
Bumblebiber/o9k-session-start
development
VerifiedTrustedCommunity
Mandatory entry point for every Cortex session — invoke at conversation start, after /clear, and after any load_project call. All stable context (H-entries, projects, device, sync) is pre-injected by the hook — no read_memory(mode='essentials') needed. Surfaces pending git work, Next Steps + open T-tasks, and runs the O-entry routing check.
19SKILL.mdUpdated May 12, 2026
Bumblebiber/o9k-curate
tools
VerifiedTrustedCommunity
Curate an .hmem file (your own or foreign) — mark obsolete/irrelevant, fix titles, consolidate duplicates, repair broken links. **Requires the `hmem-curate` MCP server** (skill prompts the user to enable it on entry). Use whenever the user says 'aufräumen', 'memory aufräumen', 'Speicher aufräumen', 'hmem aufräumen', 'clean up memory', 'tidy up hmem', 'curate memory', 'consolidate duplicates', 'merge duplicate entries', 'fix broken links', 'kümmer dich um die Memory', or invokes /o9k-curate. Also trigger when `memory_health()` flags BLOCKER/WARNING issues, when a P-entry's load_project output exceeds 4k tokens (session-start noise check defers to this skill), or before any batch cleanup of L, E, D, P entries. Skipping this skill and editing memory directly bypasses health checks, severity triage, and obsolete-chain integrity — never curate without it.
19SKILL.mdUpdated May 12, 2026
Bumblebiber/o9k-new-rule
testing
VerifiedTrustedCommunity
Add a new rule and place it correctly — decide between a cross-project R-entry and a project-specific subnode under the active project's Rules section. Use whenever the user says 'neue Regel', 'Regel hinzufügen', 'new rule', 'add a rule', or invokes /o9k-new-rule. Critical safeguard: project-specific rules placed as R-entries pollute the session-start Rules listing across every project — get the scope right BEFORE writing.
18SKILL.mdUpdated May 21, 2026