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 devrel-playbookgit 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/devrel-playbook)<a href="https://agentmods.dev/skills/gingiris-1031/gingiris-skills/devrel-playbook"><img src="https://agentmods.dev/badge/skills/gingiris-1031/gingiris-skills/devrel-playbook/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/devrel-playbook"><img src="https://agentmods.dev/badge/skills/gingiris-1031/gingiris-skills/devrel-playbook.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.00057 | $0.01170 |
| Opus 5.5 | $0.00023 | $0.00468 |
| Sonnet 5.5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
devrel-playbook 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 6d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevRel Playbook — Developer Activation, Community and Revenue
DevRel exists to reduce the distance between a developer's first exposure and sustained product value. Do not optimize only for members, event attendance or impressions.
Diagnose the bottleneck
Choose one primary problem:
| Problem | Evidence | First intervention |
|---|---|---|
| Discovery | ICP developers do not know the project | technical content and ecosystem distribution |
| Understanding | Docs traffic is high, quickstart completion is low | README/docs usability tests |
| Activation | Keys/SDK installed, first successful call is low | sample app and error-path repair |
| Retention | Developers try once and disappear | use-case education, office hours, lifecycle prompts |
| Contribution | Users want changes but do not contribute | issue design, maintainer SLA, contributor onboarding |
| Enterprise pull | Teams use product but procurement is invisible | usage-qualified account handoff to sales |
Developer journey instrumentation
Track:
source → docs/README visit → quickstart start → first success → second session → production use → contribution/qualified account
Define each event and cohort window. Separate employees, bots, test accounts and event attendees who never touched the product.
Documentation system
Maintain four layers:
- README: outcome, demo, quickstart, license and support path;
- Tutorial: one job completed end to end;
- How-to: focused operational tasks and integrations;
- Reference: complete APIs, errors, limits and versions.
Run five-developer task tests quarterly. Record completion time, failure step, search terms and recovery success. Documentation is a product surface, not a publishing queue.
Community operating model
- Assign owner and response SLA for support, bugs and feature discussions.
- Separate announcements, help, showcase and contributor channels.
- Turn repeated questions into docs; turn reproducible bugs into issues.
- Recognize substantive help, not message volume.
- Publish moderation and escalation rules before growth.
What ships with it
5 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.
- 6d ago Changed · +14 lines 6d64ddf7a125
- 1mo ago Changed · +56 lines · +10 tokens per session b9b7a50749bf
- 1mo ago First seen · 49 lines · 47 tokens per session scan A 9ba8cae8ed0b
devrel-playbook is a skill published in the GitHub repository Gingiris-1031/gingiris-skills (86 stars, last pushed 6d ago), licensed MIT. It adds 57 tokens to every session and 1,170 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.
Other skills, from other repositories
marketing-director
The Chief Marketing Officer (CMO) — manages ALL marketing activities across 1ai-social and 1ai-ads. Delegates to paid ads, content marketing, email marketing, social media, SEO, and analytics. Has memory via 1ai-hub brain, follows 1ai-rules, and coordinates with Content Director for content production and Sales…
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…
channel-discovery
Use this skill to identify and score acquisition channels by audience fit, speed, cost, effort, and learning value, then recommend the top three. Trigger it when choosing where to reach a defined audience, planning go-to-market, or replacing an underperforming channel.