Prompt example extracted from OpenAI Cookbook.
Using gpt-oss-safeguard for Trust & Safety Because gpt-oss-safeguard interprets written rules rather than static categories, gpt-oss-safeguard adapts to different product, regulatory, and community contexts with minimal engineering overhead. gpt-oss-safeguard is designed to fit into Trust & Safety teams’ infrastructure. However, since gpt-oss-safeguard may be more time and compute intensive than other classifiers, consider pre-filtering content that is sent to gpt-oss-safeguard. [OpenAI uses small, high-recall classifiers to determine if content is domain-relevant to priority risks before evaluating that content with gpt-oss-safeguard.](https://openai.com/index/introducing-gpt-oss-safeguard/) You should consider two main things when deciding when and where to integrate oss-safeguard in your T\&S stack: 1. Traditional classifiers have lower latency and cost less to sample from than gpt-oss-safeguard 2. Traditional classifiers trained on thousands of examples will likely perform better on a task than gpt-oss-safeguard
