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 skills add CarbeneAI/Forge --skill algorithmgit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/algorithm)<a href="https://agentmods.dev/skills/carbeneai/forge/algorithm"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/algorithm/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/carbeneai/forge/algorithm"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/algorithm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00046 | $0.03102 |
| Opus 5.5 | $0.00018 | $0.01241 |
| Sonnet 5.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 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.
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.
- 1mo 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 2mo ago), licensed MIT. It adds 46 tokens to every session and 3,102 once invoked, about $0.0002 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.
Other skills, from other repositories
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.
panguard
AI agent security platform — audit skills, scan for threats, and run 24/7 protection with 9,700+ detection rules.
detecting-aws-credential-exposure-with-trufflehog
Detecting exposed AWS credentials in source code repositories, CI/CD pipelines, and configuration files using TruffleHog, git-secrets, and AWS-native detection mechanisms to prevent credential theft and unauthorized account access.