What is github-lead-qualification?

A GitHub lead-qualification procedure for deciding whether potential organizations fit a product's target customer profile. It uses existing Airtable records and evidence to assign a fit category.

Reviewing existing GitHub lead candidates, marking them as a fit, possible fit, or not a fit, and updating their priority, status, evidence, and next action.

It prevents unsuitable prospects from moving into outreach and keeps qualification decisions traceable. It also assigns the next step for each candidate.

How Ducksss/codex-profiles configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to Ducksss/codex-profiles. 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/Ducksss/codex-profiles/main/.agents/skills/github-lead-qualification/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Ducksss/codex-profiles

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ducksss/codex-profiles/github-lead-qualification/github.svg)](https://agentmods.dev/skills/ducksss/codex-profiles/github-lead-qualification)

Your own site

<a href="https://agentmods.dev/skills/ducksss/codex-profiles/github-lead-qualification"><img src="https://agentmods.dev/badge/skills/ducksss/codex-profiles/github-lead-qualification/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ducksss/codex-profiles/github-lead-qualification"><img src="https://agentmods.dev/badge/skills/ducksss/codex-profiles/github-lead-qualification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,144 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.01144
Opus 5.5	$0.00017	$0.00458
Sonnet 5.5	$0.00009	$0.00229
Haiku 4.5	$0.00004	$0.00114

Measured 2mo ago against content hash 0f84bbd8f54d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github-lead-qualification 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 2mo 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.

.agents/skills/github-lead-qualification/SKILL.md · 105 lines

How it starts

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

GitHub Lead Qualification

Purpose

Decide whether GitHub lead-gen candidates are real fits for codex-profiles, then update the outreach tracker with evidence and a next phase. This skill consumes tracker targets whose Next Action = Run lead qualification.

Required Context

Read README.md for current product positioning, ops/outreach/launch.md for policy gates, and the selected tracker target for live outreach state. Load references/icp-rules.md before scoring.

Boundaries

Update tracker Targets and append Log entries only.
Consume tracker targets whose Next Action = Run lead qualification.
Use Log.Workflow = lead-qualification for every meaningful decision.
Assign exactly one of ICP: yes, ICP: maybe, or ICP: no.
Set Priority, Status, Last Checked, Next Action, and evidence.
Do not discover new leads.
Do not draft PRs, issues, comments, emails, DMs, forum posts, listing submissions, or maintainer replies.
Do not contact externally.

Accepted Input

Consume only Backlog or Deferred targets whose Next Action = Run lead qualification.
Leave ready ICP: yes targets as Backlog with Next Action = Run closing draft; leave all other outcomes with a concrete recheck, blocker, or terminal next action.
Issue-first is a valid closing-draft route when the target is a truthful fit, requires an issue before a PR, and has no existing submission.

Tracker Protocol

Create a unique run-<UTC-timestamp>-<random-suffix> <run-id>, list candidate rows, and inspect each selected row before claiming it:

node scripts/outreach-tracker.mjs list --json
node scripts/outreach-tracker.mjs list --status Backlog --json
node scripts/outreach-tracker.mjs list --status Deferred --json
node scripts/outreach-tracker.mjs get <key> --json
node scripts/outreach-tracker.mjs claim <key> --by <run-id>

If claim exits 3, skip the target without writing or contacting externally. After a successful claim, use a shell trap or equivalent finally cleanup to release on every exit path, including partial persistence or logging failure. After qualification, persist the decision and stable phase log:

Read the full file on GitHub · 105 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.

2mo ago Changed 0f84bbd8f54d
2mo ago Changed · -1 lines · +1 tokens per session fb2f9ead4fa6
2mo ago First seen · 106 lines · 42 tokens per session scan A 66df6960b31b

Subscribe to this mod's changes

github-lead-qualification is a skill published in the GitHub repository Ducksss/codex-profiles (193 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 1,144 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-30.

Marketing and SEO bash cli codex developer-tools macos openai

github-lead-qualification next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
github-lead-qualificationDucksss/codex-profiles	Skill	193	3d ago	MIT	A	43	Codex
claw-adminx-cmd/x-cmd	Skill	4.7k	6d ago	Apache-2.0	A	48	Claude Code, Codex
x-netsx-cmd/x-cmd	Skill	4.7k	6d ago	Apache-2.0	A	69	Claude Code, Codex
installx-cmd/x-cmd	Skill	4.7k	6d ago	Apache-2.0	A	99	Claude Code, Codex
x-themex-cmd/x-cmd	Skill	4.7k	6d ago	Apache-2.0	A	74	Claude Code, Codex
x-arpx-cmd/x-cmd	Skill	4.7k	6d ago	Apache-2.0	A	64	Claude Code, Codex
x-lsofx-cmd/x-cmd	Skill	4.7k	6d ago	Apache-2.0	A	64	Claude Code, Codex

codex-profiles: Skill for Codex