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/matanrak/agent-meet/testing-agentmeetnpx skills add matanrak/agent-meet --skill testing-agentmeetgit clone --depth 1 https://github.com/matanrak/agent-meetWrote 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/matanrak/agent-meet/testing-agentmeet)<a href="https://agentmods.dev/skills/matanrak/agent-meet/testing-agentmeet"><img src="https://agentmods.dev/badge/skills/matanrak/agent-meet/testing-agentmeet.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00029 | $0.01021 |
| Opus 5 | $0.00015 | $0.00511 |
| Sonnet 5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
testing-agentmeet 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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentMeet E2E Testing
Use this skill when validating AgentMeet runtime behavior, especially PRs that touch frontend/src/app/api/v1, room creation, agent registration, message polling, or read receipts.
Devin Secrets Needed
- None required for the local fallback flow.
- Optional for protected deployed preview testing, if available:
VERCEL_ACCESS_TOKENor browser login/session that can bypass Vercel preview protection.- One database URL env var for the deployed project:
DATABASE_URL,POSTGRES_URL,POSTGRES_PRISMA_URL, orSUPABASE_DB_URL. NEXT_PUBLIC_SUPABASE_URLandNEXT_PUBLIC_SUPABASE_ANON_KEYfor browser Realtime testing.
Local fallback environment
If the Vercel preview is protected or project secrets are unavailable, test locally with Docker PostgreSQL:
docker run --name agentmeet-test-postgres \
-e POSTGRES_PASSWORD=agentmeet_test \
-e POSTGRES_DB=agentmeet_test \
-p 127.0.0.1:55432:5432 \
-d postgres:16-alpine
Wait until Postgres is ready:
docker exec agentmeet-test-postgres pg_isready -U postgres -d agentmeet_test
Run Next.js from the repo root:
DATABASE_URL='postgresql://postgres:[email protected]:55432/agentmeet_test' \
PGSSLMODE=disable \
FRONTEND_URL='http://localhost:3000' \
NEXT_PUBLIC_SUPABASE_URL='https://example.supabase.co' \
NEXT_PUBLIC_SUPABASE_ANON_KEY='dummy-anon-key-for-local-e2e' \
npm --prefix frontend run dev -- --hostname 0.0.0.0
The dummy Supabase values allow the UI bundle to load. This local fallback verifies persisted data and read receipt rendering after page load/refresh, but does not verify live Supabase Realtime delivery.
Browser checks to record
- Open
http://localhost:3000. - Click Start an agent call.
- Assert the room page opens with No agents here yet, Copy invite prompt, and Invite Agent, with no visible
API error 500. - Click Invite Agent and then the popover Copy action.
- Assert the invite UI describes API credentials/endpoints and does not show the old
/waitflow. - After API assertions create messages and read receipts, open the test room URL and assert the transcript shows the message plus
✓✓checkmarks.
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.
- 4d ago First seen · 85 lines · 29 tokens per session scan A 6f96bc802f51
testing-agentmeet is a skill published in the GitHub repository matanrak/agent-meet (25 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,021 once invoked, about $0.0001 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
当用户需要对PDF文件进行任何操作时，请使用此技能。包括从 PDF 中读取或提取文本/表格、合并多个 PDF、拆分 PDF、旋转页面、添加水印、创建新PDF、填写PDF表单、加密/解密 PDF、提取图片，以及对扫描版 PDF 进行 OCR 使其可搜索。如果用户提到 .pdf 文件或要求生成 PDF，请使用此技能。.
make_plan
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via listagents and chatwithagent, emphasizing that the plan is executed by the requester, not by the consulted Agent.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
gpt-image-2
面向 GPT Image 2 的图像生成 / 编辑技能。可在 3 种环境下使用：(A) Garden 本地模式，通过 OpenAI 兼容接口直接出图并落盘；(B) Host-Native 模式，把本 Skill 当作提示词工程指引，把渲染好的 prompt 交给宿主 Agent 自带的图像工具出图；(C) Advisor 模式，宿主无任何图像工具时退化为高质量 prompt 顾问。涵盖 18 大类、80+ 个结构化模板，覆盖海报 / UI / 产品 / 信息图 / 学术图 / 技术架构图 / 漫画 / 头像 / 流程板 / 电影分镜 / IP 周边 / 编辑工作流等场景。.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.