free-tool-strategy

free-tool-strategy is a skill for Claude Code, Codex from zocomputer/skills. It costs 93 tokens per session (2,682 once invoked), scanned A, a copy of free-tool-strategy, MIT.

A set of instructions for using GitHub through its command-line tool, including issues, pull requests, automated checks, and workflow runs. GitHub is a service for hosting code and managing collaborative development.

In plain words
What is it for?
Use it to inspect pull requests, review CI results, list issues, view failed workflow logs, and query GitHub data.
Why use it?
It avoids switching between GitHub's website and the terminal when checking project work or automation results.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect pull requests, review CI results, list issues, view failed workflow logs, and query GitHub data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zocomputer/skills/free-tool-strategy
Install

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.

Any agent
npx skills add zocomputer/skills --skill free-tool-strategy
Clone the repo
git clone --depth 1 https://github.com/zocomputer/skills

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/zocomputer/skills/free-tool-strategy/github.svg)](https://agentmods.dev/skills/zocomputer/skills/free-tool-strategy)
Your own site
<a href="https://agentmods.dev/skills/zocomputer/skills/free-tool-strategy"><img src="https://agentmods.dev/badge/skills/zocomputer/skills/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/zocomputer/skills/free-tool-strategy"><img src="https://agentmods.dev/badge/skills/zocomputer/skills/free-tool-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,682 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 98% 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.00093 $0.02682
Opus 5 $0.00046 $0.01341
Sonnet 5 $0.00019 $0.00536
Haiku 4.5 $0.00009 $0.00268

Measured 5d ago against content hash d66937aa3a93, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 5d 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

98% identical to free-tool-strategy — 3 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.

External/free-tool-strategy/SKILL.md · 580 lines

How it starts

The opening of the file, as written. The whole thing — 580 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

Before designing a tool strategy, understand:

  1. Business Context

    • What's the core product/service?
    • Who is the target audience?
    • What problems do they have?
  2. Goals

    • Lead generation primary goal?
    • SEO/traffic acquisition?
    • 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
  • Consider SEO value
  • Consider brand halo effect

Tool Types

Calculators

Best for: Decisions involving numbers, comparisons, estimates

Examples:

  • ROI calculator
  • Savings calculator
  • Cost comparison tool
  • Salary calculator
  • Tax estimator

Why they work:

  • Personalized output
  • High perceived value
  • Share-worthy results
  • Clear problem → solution

Generators

Best for: Creating something useful quickly

Examples:

  • Policy generator
  • Template generator
  • Name/tagline generator
  • Email subject line generator
  • Resume builder

Why they work:

  • Tangible output
  • Saves time
  • Easily shared
  • Repeat usage

Analyzers/Auditors

Best for: Evaluating existing work or assets

Examples:

  • Website grader
  • SEO analyzer
  • Email subject tester
  • Headline analyzer
  • Security checker

Why they work:

  • Curiosity-driven
  • Personalized insights
  • Creates awareness of problems
  • Natural lead to solution

Read the full file on GitHub · 580 lines

Files

What ships with it

1 file 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. 5d ago First seen · 580 lines · 93 tokens per session scan A d66937aa3a93

Subscribe to this mod's changes

free-tool-strategy is a skill published in the GitHub repository zocomputer/skills (45 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 2,682 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to free-tool-strategy, differing in 3 lines, and is treated as a copy.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

codex-autoresearch

Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…

leo-lilinxiao/codex-autoresearch · 80 tokens