HoloCore: Skill for Claude Code

.agents/skills/holocore-uninstall/SKILL.md

holocore-uninstall is a skill for Claude Code, Codex from HassanMahomed/HoloCore. It costs 19 tokens per session (96 once invoked), scanned A, original, Apache-2.0.

A command for removing the HoloCore command-line tool while keeping project and home data.

In plain words
What is it for?
Use it when uninstalling HoloCore without deleting registered project data or home data.
Why use it?
It separates removal of the tool from removal of the information it uses.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is HassanMahomed/HoloCore's own configuration. It tells Claude Code and Codex how to work on HoloCore itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything HoloCore configures →

Reuse

Borrowing it

Nothing to install: this file belongs to HassanMahomed/HoloCore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/HassanMahomed/HoloCore/main/.agents/skills/holocore-uninstall/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/HassanMahomed/HoloCore

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for holocore-uninstall

README.md
[![agentmods](https://agentmods.dev/badge/skills/hassanmahomed/holocore/holocore-uninstall/github.svg)](https://agentmods.dev/skills/hassanmahomed/holocore/holocore-uninstall)
Your own site
<a href="https://agentmods.dev/skills/hassanmahomed/holocore/holocore-uninstall"><img src="https://agentmods.dev/badge/skills/hassanmahomed/holocore/holocore-uninstall/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.

agentmods 80×15 button for holocore-uninstall

Your own site · 80×15
<a href="https://agentmods.dev/skills/hassanmahomed/holocore/holocore-uninstall"><img src="https://agentmods.dev/badge/skills/hassanmahomed/holocore/holocore-uninstall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 96 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00096
Opus 5.5 $0.00008 $0.00038
Sonnet 5.5 $0.00004 $0.00019
Haiku 4.5 $0.00002 $0.00010

Measured 1mo ago against content hash 1d85d64ea0d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

holocore-uninstall 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 1mo 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.

.agents/skills/holocore-uninstall/SKILL.md · 17 lines

What it actually says

holocore-uninstall

Remove the HoloCore CLI while preserving project and Home data.

This may write project data; confirm the requested scope before running it.

Interpret any details following the skill mention as the user's arguments. Run the corresponding command from the project root, adding those arguments where appropriate:

holocore uninstall
Changes

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.

  1. 1mo ago First seen · 17 lines · 19 tokens per session scan A 1d85d64ea0d6

Subscribe to this mod's changes

holocore-uninstall is a skill published in the GitHub repository HassanMahomed/HoloCore (4 stars, last pushed 16d ago), licensed Apache-2.0. It adds 19 tokens to every session and 96 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

weekly-digests

Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…

thedotmack/claude-mem · 93 tokens

version-bump

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…

thedotmack/claude-mem · 64 tokens

cloud-sync

Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.

thedotmack/claude-mem · 64 tokens

repomix

Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.

yamadashy/repomix · 58 tokens

ix

Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.

ix-infrastructure/Ix · 44 tokens

services-audit-cron

Use when scheduling the canonical biweekly services-audit cron loop for Empirica's AI service scanner (Phase 3). The auditor body is empirica services-audit — captures a fresh scan, diffs against the previous, and emits a notification when novel running services appear. This skill provides the prompt template that…

EmpiricaAI/empirica · 126 tokens