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 agentmods add skills/hashgraph-online/awesome-codex-plugins/getting-startednpx skills add hashgraph-online/awesome-codex-plugins --skill getting-startedgit clone --depth 1 https://github.com/hashgraph-online/awesome-codex-pluginsWhat 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 | $0.00059 | $0.00385 |
| Opus 5 | $0.00030 | $0.00192 |
| Sonnet 5 | $0.00012 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
getting-started 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 2d 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.
What it actually says
Getting Started with Agiflow
Act as a project-management coach. Diagnose the workspace before recommending action.
Workflow
- Call
get_current_scopeto identify the organization and current project context. - If the user has not selected a project, call
list_projectsand ask them to choose when more than one plausible project exists. - For the selected project, call
get_project_detail,list_project_statuses,list_work_units, andlist_tasks. - Call
list_membersonly when assignments or team capacity affect the recommendation. - Interpret the state instead of only repeating counts.
- Recommend one primary next workflow and explain why it fits.
Decision Guide
- Empty project or unstructured requirements: use
project-plan. - Vague Planning task or unclear completion criteria: use
refine-task. - Ready Planning tasks that need prioritization or grouping: use
backlog-grooming. - Stalled, blocked, overloaded, or unhealthy work: use
triage. - Quick read-only progress check: use
daily-standup.
Response
Summarize:
- Current scope and project
- Important workspace signals
- Main risk or ambiguity
- Recommended workflow
- One concrete next prompt the user can send
Guardrails
- Do not create or modify records during orientation.
- Do not assume status names. Read them with
list_project_statuses. - Ask a focused question when the desired outcome or project is unclear.
- Keep recommendations scoped to capabilities exposed by the Agiflow plugin.
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.
- 2d ago First seen · 43 lines · 59 tokens per session scan A 6965f91c31ad
getting-started is a skill published in the GitHub repository hashgraph-online/awesome-codex-plugins (859 stars, last pushed 4d ago), licensed Apache-2.0. It adds 59 tokens to every session and 385 once invoked, about $0.0003 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
search
Search 2500+ curated ChatGPT and LLM open-source repositories. Use when the user asks to find tools, libraries, or repos related to ChatGPT, LLMs, RAG, agents, langchain, NLP, AI development, or any open-source AI tooling.
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
dsh-topic-curator
Scan the GitHub dsh-plugin topic for new DeepSeek Harness community extensions, diff them against the local catalog CSVs, dispatch parallel review agents, and merge qualifying repos (above the star floor) into repositories.csv / dsh-plugin-topic-candidates.csv / verified-plugins.csv per the project's curation rules.…
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
coordinate
Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.