ghostclaw: Skill for Claude Code

.claude/skills/free-tool-strategy/SKILL.md

free-tool-strategy is a skill for Claude Code from b1rdmania/ghostclaw. It costs 136 tokens per session (1,316 once invoked), scanned A, a copy of free-tool-strategy, MIT.

A planning guide for creating a free software tool that supports marketing, such as a calculator, generator, or other interactive utility.

In plain words
What is it for?
Use it to assess the product, audience, goal, resources, and fit before planning a free tool and its promotion.
Why use it?
It helps connect the tool to a real audience problem and a business goal, such as attracting search traffic, generating leads, or building awareness.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is b1rdmania/ghostclaw's own configuration. It tells Claude Code how to work on ghostclaw 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 ghostclaw configures →

Reuse

Borrowing it

Nothing to install: this file belongs to b1rdmania/ghostclaw. 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/b1rdmania/ghostclaw/main/.claude/skills/free-tool-strategy/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/b1rdmania/ghostclaw

Made for: Claude Code.

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 free-tool-strategy

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/b1rdmania/ghostclaw/free-tool-strategy"><img src="https://agentmods.dev/badge/skills/b1rdmania/ghostclaw/free-tool-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 136 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,316 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 94% copy Near-identical to another mod 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.00136 $0.01316
Opus 5 $0.00068 $0.00658
Sonnet 5 $0.00027 $0.00263
Haiku 4.5 $0.00014 $0.00132

Measured 9d ago against content hash a9aa55a24d19, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

free-tool-strategy 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 9d 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.

Origin

This is a copy

94% identical to free-tool-strategy — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/free-tool-strategy/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Free Tool Strategy (Engineering as Marketing)

You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before designing a tool strategy, understand:

  1. Business Context - What's the core product? Who is the target audience? What problems do they have?

  2. Goals - Lead generation? SEO/traffic? Brand awareness? Product education?

  3. Resources - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?


Core Principles

1. Solve a Real Problem

  • Tool must provide genuine value
  • Solves a problem your audience actually has
  • Useful even without your main product

2. Adjacent to Core Product

  • Related to what you sell
  • Natural path from tool to product
  • Educates on problem you solve

3. Simple and Focused

  • Does one thing well
  • Low friction to use
  • Immediate value

4. Worth the Investment

  • Lead value × expected leads > build cost + maintenance

Tool Types Overview

Type Examples Best For
Calculators ROI, savings, pricing estimators Decisions involving numbers
Generators Templates, policies, names Creating something quickly
Analyzers Website graders, SEO auditors Evaluating existing work
Testers Meta tag preview, speed tests Checking if something works
Libraries Icon sets, templates, snippets Reference material
Interactive Tutorials, playgrounds, quizzes Learning/understanding

For detailed tool types and examples: See references/tool-types.md


Ideation Framework

Read the full file on GitHub · 179 lines

Files

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.

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. 9d ago First seen · 179 lines · 136 tokens per session scan A a9aa55a24d19

Subscribe to this mod's changes

free-tool-strategy is a skill published in the GitHub repository b1rdmania/ghostclaw (92 stars, last pushed 4mo ago), licensed MIT. It adds 136 tokens to every session and 1,316 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to free-tool-strategy, differing in 7 lines, and is treated as a copy.

Related

Other skills, from other repositories

lobu-operator

Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.

lobu-ai/lobu · 0 tokens

company-agent-infrastructure

Use when designing or building internal/company AI agents that need shared context across company systems, durable organizational memory across sessions or agents, user-scoped permissions, approvals, audit, or governed actions. Also use when deciding whether ordinary MCP tools, RAG, or local agent memory are enough…

lobu-ai/lobu · 70 tokens

lobu-builder

Use when working inside a Lobu project generated by @lobu/cli or any repository centered on lobu.config.ts, AGENTS.md, agent prompt files, local skills, and evals. This skill helps a coding agent inspect the right files, make Lobu-native changes, keep the stack runnable, and validate semantics with chat tests and…

lobu-ai/lobu · 76 tokens

crm-ops

How to operate the Lobu funnel CRM — create and enrich leads, log interactions, advance funnel stages, open and update pilots, and produce the weekly digest. Use whenever the task touches the pipeline.

lobu-ai/lobu · 44 tokens

deliveroo-order

Turn collected lunch orders into a clean per-person order list for a human to place on Deliveroo. Use in step 2 of the lunch run, after orders are collected. The live menu is fetched automatically by the lobu-team-lunch-finalize reaction (via the Owletto Chrome extension) — this skill never places an order or touches…

lobu-ai/lobu · 75 tokens

lobu

Use Lobu MCP for shared, permission-aware company context, durable organizational memory, and governed actions. Trigger when the user asks what the organization knows, needs context from connected company systems, wants to preserve a durable fact or decision, or needs to discover and use Lobu SDK capabilities.

lobu-ai/lobu · 60 tokens