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 skills/carbeneai/forge/algorithmnpx skills add CarbeneAI/Forge --skill algorithmgit clone --depth 1 https://github.com/CarbeneAI/ForgeWhat 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.00046 | $0.03102 |
| Opus 5 | $0.00023 | $0.01551 |
| Sonnet 5 | $0.00009 | $0.00620 |
| Haiku 4.5 | $0.00005 | $0.00310 |
Grade A, and why
Algorithm 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 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.
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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Algorithm
A structured 7-phase execution framework for systematic problem-solving. The Algorithm skill provides a rigorous, repeatable methodology for approaching any task - from trivial to complex - with appropriate depth based on effort classification.
Core Philosophy
Every problem deserves the right amount of rigor.
The Algorithm framework scales from TRIVIAL tasks (minutes of effort) to DETERMINED challenges (multi-day investigations) by adjusting the depth of each phase while maintaining consistent structure.
The 7 Phases
The Algorithm consists of seven sequential phases, each with clear inputs, actions, outputs, and exit criteria:
1. OBSERVE
Purpose: Gather facts and understand the current state.
- Input: Problem statement or task description
- Actions: Read, investigate, measure, document current state
- Output: Factual understanding of what exists now
- Exit criteria: Can describe problem objectively without interpretation
2. THINK
Purpose: Analyze, reason, and form hypotheses.
- Input: Observations from OBSERVE phase
- Actions: Analyze patterns, identify root causes, generate theories
- Output: Understanding of why things are the way they are
- Exit criteria: Have working theory of causation and relationships
3. PLAN
Purpose: Design solution approach and implementation strategy.
- Input: Understanding from THINK phase
- Actions: Design solution, sequence steps, identify resources
- Output: Detailed implementation plan with success criteria
- Exit criteria: Clear roadmap from current state to desired state
4. BUILD
Purpose: Create the solution components.
- Input: Plan from PLAN phase
- Actions: Write code, create documents, build infrastructure
- Output: Working implementation of solution
- Exit criteria: All planned components exist and are integrated
5. EXECUTE
Purpose: Run the solution in target environment.
- Input: Built solution from BUILD phase
- Actions: Deploy, configure, launch, operate
- Output: Solution running in production/real environment
- Exit criteria: System operational and handling real work
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 381 lines · 46 tokens per session scan A dbda8e6a2d41
Algorithm is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 3,102 once invoked, about $0.0002 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
pentesting-everything
Guides authorized penetration testing with PentestingEverything as the source-grounded knowledge base. Use when scoping an engagement, building domain checklists, hunting a vulnerability class, choosing tools/commands, or drafting evidence-based findings from this repository's Markdown.
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
hunt-ato
Hunt account takeover taxonomy — 9 distinct paths to ATO, plus chains. Paths: (1) password reset flaws (host-header injection redirects token, predictable/numeric token, Referer leak, no-expiry/reuse), (2) email change without re-auth, (3) OAuth account-link CSRF, (4) MFA bypass (per hunt-mfa-bypass), (5) session…
aod-orchestrate
Multi-feature orchestration skill that bridges /aod.blueprint output to parallel wave execution. Groups synced GitHub Issues by ICE priority tier (P0/P1/P2) into sequential waves, creates Task records, spawns batch sessions via the orchestrator API, monitors completion, and reports results. Supports --issues…
security
Claude-powered SAST and SCA security scan skill. Invoked automatically as the Security Scan step (Step 7) of /aod.build (after Design Quality Gate, before Code Simplification) or standalone via /security. Analyzes all code files and dependency manifests changed on the feature branch relative to main for OWASP Top 10…
aod-foundation
Guided post-init workshop that helps new AOD Kit adopters establish product vision and design identity. Two-part flow: Part 1 (Vision) asks 5 guided questions to populate product-vision.md; Part 2 (Design) browses archetypes to generate brand files (brand.md, tokens.css, anti-patterns.md). Supports --vision and…