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/hamr0/agentic-toolkit/internal-commsnpx skills add hamr0/agentic-toolkit --skill internal-commsgit clone --depth 1 https://github.com/hamr0/agentic-toolkitWhat 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.00067 | $0.00321 |
| Opus 5 | $0.00034 | $0.00161 |
| Sonnet 5 | $0.00013 | $0.00064 |
| Haiku 4.5 | $0.00007 | $0.00032 |
Grade A, and why
internal-comms 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.
This is a copy
83% identical to internal-comms — 2 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.
What it actually says
When to use this skill
To write internal communications, use this skill for:
- 3P updates (Progress, Plans, Problems)
- Company newsletters
- FAQ responses
- Status reports
- Leadership updates
- Project updates
- Incident reports
How to use this skill
To write any internal communication:
- Identify the communication type from the request
- Load the appropriate guideline file from the
examples/directory:examples/3p-updates.md- For Progress/Plans/Problems team updatesexamples/company-newsletter.md- For company-wide newslettersexamples/faq-answers.md- For answering frequently asked questionsexamples/general-comms.md- For anything else that doesn't explicitly match one of the above
- Follow the specific instructions in that file for formatting, tone, and content gathering
If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
Keywords
3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms
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.
- 2d ago First seen · 33 lines · 67 tokens per session scan A 067b7587a344
internal-comms is a skill published in the GitHub repository hamr0/agentic-toolkit (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 67 tokens to every session and 321 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to internal-comms, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
create_profile_style_skill
【META SKILL】分析当前剪辑逻辑与风格，总结并生成一个新的可复用 Skill 文件，存入剪辑技能库。Analyze the current editing logic and style, summarize and generate a new reusable Skill file, and store it in the editing skill library.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
Paper Writing Workflow
Workflow phases for paper-writing tasks: triage, material inventory, research question, literature review, paper outline, data analysis summary, figure storyline, reader testing, and finalize packet. Each phase is a short contract — read the relevant rows for the current task only.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.