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 CodeInfinity1/Stram --skill polymarketgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/polymarket)<a href="https://agentmods.dev/skills/codeinfinity1/stram/polymarket"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/polymarket/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/codeinfinity1/stram/polymarket"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/polymarket.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.00486 |
| Opus 5.5 | $0.00014 | $0.00194 |
| Sonnet 5.5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
polymarket 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 1mo 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
75% identical to shop-app — 30 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polymarket
This is a Stram-native skill. It is authored inside this repository and uses only Stram-owned tools, approval gates, artifacts, and optional dependency records.
When To Use
Use this skill when the user asks for polymarket planning, execution, verification, troubleshooting, or artifact creation inside Stram.
Tool Map
tool_searchtool_describecapability_surfacewrite_notenative_security_policytool_output_storepolymarket_query_prepareweb_searchweb_extractresearch_web_pagesx_searchprovider_registryexecute_codecredential_file_policy
Workflow
- Clarify the user's concrete polymarket objective, target environment, credentials already configured, and expected artifact or action.
- Use
tool_searchorcapability_surfaceto find the native Stram tools for the domain before choosing a path. - Run safe inspection/readiness steps first and write bounded notes or artifacts under the workspace or data directory.
- Collect sources with web/research tools, store evidence, and separate verified facts from hypotheses.
- For security or OSINT work, use defensive scope, authorization notes, and credential-file policy records before running active checks.
- Summarize what ran, what was skipped, what remains blocked, and the exact files or records created.
Safety And Boundaries
- Do not import, execute, or vendor upstream assistant code for this skill.
- Do not store raw secrets; store only environment variable names, secret references, or readiness booleans.
- Use approvals for writes, sends, purchases, desktop control, process launches, provider calls, and destructive operations.
- Do not run network scans, exploit tooling, cloud jobs, or GPU workloads without explicit authorization and scope.
Verification
- Record concrete evidence paths or tool outputs before claiming completion.
- Prefer dry-run or prepared artifacts when credentials, hardware, licenses, or live services are missing.
- If a provider-specific runtime is not configured, report the missing credential or binary by name and stop before live execution.
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.
- 1mo ago First seen · 52 lines · 36 tokens per session scan A 93766e279d05
polymarket is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 486 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 75% identical to shop-app, differing in 30 lines, and is treated as a copy.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
business-design
Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use design-negotiation (designer-toolkit).
monetization-strategy
Revenue models, pricing strategies, and business monetization. Use when designing pricing, choosing business models, or optimizing revenue for products and services.
agent-payment-billing-specialist
Specialist subagent: Stripe integration, subscription billing, webhooks, PCI compliance, and tax handling specialist. Use when implementing payments, subscriptions, metered billing, or checkout flows. Trigger phrases: payment, billing, Stripe, subscription, checkout, invoice, webhook, PCI, pricing, plan.
financial-scenario-planner
Stress-test financial plans across scenarios (bull/bear/base), sensitivity tables, and Monte Carlo-style analysis. Use when evaluating financial assumptions, modeling risk scenarios, or building scenario-based financial plans.
financial-data-collector
Use when collecting financial data for a US public company, assembling DCF inputs, pulling market and filing facts, or grounding downstream analysis in structured yfinance and SEC data.