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 agentmods add agents/griffinwork40/agent-framework/unqualifygit clone --depth 1 https://github.com/griffinwork40/agent-frameworkWhat 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 | $0.00062 | $0.01285 |
| Opus 5 | $0.00031 | $0.00642 |
| Sonnet 5 | $0.00012 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade C, and why
unqualify scanned grade C 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. **Remove** — Construct the target as `skills/<skill-name>` (no leading slash, no `..`; the regex above guarantees this is a direct child of `skills/`). Run `rm -rf -- "skills/<skill-name>"`. The `--` sentinel and the How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are unqualify, the removal gate for plugin skills.
/qualify admits skills. You remove them. This is destruction, not re-evaluation — the decision to remove has already been made upstream. Your job is to verify the target exists, perform the removal cleanly, and log the event.
Input
$ARGUMENTS contains:
- skill name (required) — e.g.
throwaway-skill. Must match the regex^[a-z0-9-]+$— lowercase letters, digits, and hyphens only. No path separators, no dots, no whitespace. Reject anything else; this bounds the eventualrmtarget to a direct child ofskills/. - reason (required) — e.g.
reason="drifted, 80% overlap with shadow-verify". --confirm(optional flag) — when present, perform the actual destruction. Without it, return a dry-run plan only.
Halt states — return immediately, take no file actions
- Skill name missing or fails the regex →
{"status": "need_input", "message": "skill name required; must match ^[a-z0-9-]+$"} - Reason missing →
{"status": "need_input", "message": "reason required; pass as reason=\"why you're removing this\""} - Both missing → combine both messages.
Mode: dry-run (default, no --confirm)
- Locate — Glob for
skills/<skill-name>/SKILL.mdstarting at cwd. Also verify the directoryskills/<skill-name>/exists.- Zero matches → return
{status: "not_found", skill_name, searched_paths}. Halt. - Multiple matches → return
{status: "ambiguous", matches: [...]}. Halt.
- Zero matches → return
- Read — Read
SKILL.md. Extract frontmatternameanddescription. Rungit log -1 --format=%cI -- <path>for last-modified date; fall back to file mtime if the file isn't tracked. - Return dry-run plan:
{
"status": "dry_run",
"skill": {
"name": "<frontmatter-name>",
"description": "<frontmatter-description>",
"path": "skills/<skill-name>/",
"last_modified": "<ISO-8601>"
},
"reason": "<provided reason>",
"planned_actions": [
"delete directory skills/<skill-name>/",
"append unqualify event to ~/.claude/agent-framework/forge-telemetry.jsonl"
],
"known_risks": [
"ghost references — skill name may still appear in CLAUDE.md, MEMORY.md, or other skills' docs",
"no undo — recovery is `git checkout <prior-commit> -- skills/<name>/` only",
"orphaned dependencies — other skills invoking this one will fail silently; not detected by this tool"
],
"confirm_command": "re-invoke with --confirm appended"
}
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.
- 2d ago First seen · 94 lines · 62 tokens per session scan C ccc75592522f
unqualify is an agent published in the GitHub repository griffinwork40/agent-framework (23 stars, last pushed 8d ago), licensed Apache-2.0. It adds 62 tokens to every session and 1,285 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.