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 contentstack/contentstack-ios --skill testinggit clone --depth 1 https://github.com/contentstack/contentstack-iosWrote 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/contentstack/contentstack-ios/testing)<a href="https://agentmods.dev/skills/contentstack/contentstack-ios/testing"><img src="https://agentmods.dev/badge/skills/contentstack/contentstack-ios/testing/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/contentstack/contentstack-ios/testing"><img src="https://agentmods.dev/badge/skills/contentstack/contentstack-ios/testing.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.00024 | $0.00462 |
| Opus 5 | $0.00012 | $0.00231 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
testing 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.
What it actually says
Testing – Contentstack iOS CDA SDK
Use this skill when adding or refactoring tests in the ContentstackTest target.
When to use
- Writing new XCTest cases or methods.
- Adding bundle resources (e.g. JSON fixtures) for tests.
- Debugging flaky or slow network tests.
Instructions
XCTest and layout
- Tests live under
ContentstackTest/and compile intoContentstackTest.xctest(scheme Contentstack). - Class naming:
*Test(e.g.ContentstackMainTest,QueryAdvancedTest). - Method naming:
- (void)testFeatureNameor similar descriptive selectors.
Fixtures and credentials
- Integration-style tests often load
config.jsonfrom the test bundle (seeContentstackMainTest). Required keys should match what existing tests read (api_key,delivery_token,environment,host, etc.). - Never commit production tokens. For CI, use secrets or skip network tests when credentials are missing (follow patterns already in the suite if present).
Async and timeouts
- Use
XCTestExpectationandwaitForExpectationsWithTimeout:(orwaitForExpectations) for asynchronous stack/entry/query completion handlers. - Choose timeouts appropriate to network latency; avoid excessively short timeouts that flake on slow networks.
Unit vs integration-style
- Prefer fast, deterministic unit tests for pure logic (parsing, edge cases) when you can isolate behavior.
- Use real-stack tests sparingly and only when validating end-to-end CDA integration.
Execution
- Xcode:
⌘Uwith scheme Contentstack. - CLI:
xcodebuild -project Contentstack.xcodeproj -scheme Contentstack -destination 'platform=iOS Simulator,name=<Device>' test
References
ContentstackTest/*.m– existing patterns- Project rule:
.cursor/rules/testing.mdc - AGENTS.md – test target and command summary
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 · 49 lines · 24 tokens per session scan A 720ea481155a
testing is a skill published in the GitHub repository contentstack/contentstack-ios (3 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 462 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-09-04.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.