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 Gingiris-1031/gingiris-skills --skill oss-growth-attributiongit clone --depth 1 https://github.com/Gingiris-1031/gingiris-skillsWrote 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/gingiris-1031/gingiris-skills/oss-growth-attribution)<a href="https://agentmods.dev/skills/gingiris-1031/gingiris-skills/oss-growth-attribution"><img src="https://agentmods.dev/badge/skills/gingiris-1031/gingiris-skills/oss-growth-attribution/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/gingiris-1031/gingiris-skills/oss-growth-attribution"><img src="https://agentmods.dev/badge/skills/gingiris-1031/gingiris-skills/oss-growth-attribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.00593 |
| Opus 5 | $0.00042 | $0.00296 |
| Sonnet 5 | $0.00017 | $0.00119 |
| Haiku 4.5 | $0.00008 | $0.00059 |
Grade A, and why
oss-growth-attribution 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 10d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSS Growth Attribution
Produce an auditable growth reconstruction, not a generic marketing checklist.
Workflow
- Resolve the canonical repository and validate it against the product domain.
- Fetch GitHub repository metadata, releases, earliest commits, and timestamped stargazers.
- Build a star timeline with daily resolution around spikes and monthly resolution elsewhere.
- Search GitHub Trending, Reddit, Hacker News, Product Hunt, X, LinkedIn, Instagram, TikTok, YouTube, developer media, technical blogs, and localized communities.
- Extract original content URLs; never substitute search-result URLs when an original URL is available.
- Normalize items to the evidence schema.
- Align publication times with star velocity using the attribution model.
- Divide history into preparation, community seed, accumulation, breakout, localization/SEO, and ecosystem stages. Omit unsupported stages.
- Report representative content per channel with hook, format, audience, funnel role, and original link.
- List channels searched but not evidenced. Absence of public evidence is not proof an event never happened.
Source priority
- GitHub REST API and repository commits/releases
- Original posts, videos, launch pages, and project-owned pages
- Independent archives or channel-specific analytics pages
- Search result snippets only as discovery or dated snapshots
Use the API playbook. Follow the environment's web-access skill for browsing.
Attribution guardrails
- Label API fields and original posts as
observed. - Label cross-source temporal conclusions as
inferred. - Label percentage shares as
modeled; use ranges, never fake precision. - Do not credit a channel merely because it is common in OSS marketing.
- Treat GitHub Trending as both an outcome of prior velocity and an amplification channel.
- Do not sum overlapping platform effects as independent last-click conversions.
- Without first-party traffic, UTM, or referral logs, state uncertainty of at least ±10–15 percentage points.
- Never claim Product Hunt or Show HN impact without a canonical launch/discussion URL or strong corroboration.
What ships with it
4 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.
- 10d ago First seen · 46 lines · 83 tokens per session scan A f47f6a724bb3
oss-growth-attribution is a skill published in the GitHub repository Gingiris-1031/gingiris-skills (79 stars, last pushed 6d ago), licensed MIT. It adds 83 tokens to every session and 593 once invoked, about $0.0004 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-30.
Other skills, from other repositories
synthesis-explore
Synthesis EXPLORE stage for the Diffmode growth-tactics pipeline (fuses the blind-combination draw + emergent-mechanism derivation — formerly two separate synthesis steps — into ONE structural-check-only stage). Reads the per-run growth-factors.json (LIGHT vector DB) + synthesis-constraints.json + founder-input +…
growth-factors-mining
Builds a per-run LIGHT growth-vector database for the Diffmode growth-tactics pipeline by mining public growth case studies fresh, every run, and distilling each into atomic "growth factors" (transferable mechanisms). Clean-room — NEVER reads the proprietary tacticsDB. Outputs growth-factors.json (20-40 vectors spread…
diagnostics-intake
Fast founder-input capture for the Diffmode growth-tactics pipeline (the diagnostics stage). Produces WS/01-diagnostics/founder-input.md in the exact schema the enrichment + synthesis stages read. Two modes — (A) URL mode researches a product's website (homepage/pricing/about) plus a web-research pass to prefill the…
lite-constraints
Generates synthesis-constraints.json for the Diffmode growth-tactics pipeline by reasoning in-context over the per-run growth-factors.json (LIGHT vector DB) + founder context — the clean-room, no-Python replacement for the proprietary Python constraints generator. Emits the white-space pairs, mandatory…
ad-angles
Use this skill to brainstorm ad concepts across problem, solution, comparison, proof, and curiosity angles, formats, and visual styles. Trigger it when planning a campaign, refreshing stale creative, testing messaging, or preparing creative briefs.
conversion-audit
Use this skill to run a scored 53-point conversion audit covering customer focus, narrative, copy, design, calls to action, and proof. Trigger it when a landing, sales, product, or ad destination page needs diagnosis, pre-launch review, or prioritized conversion fixes.